The unibase.ini file allows use of the over 100 customization environment variables by user if necessary. Almost as soon as users obtained release 7.4i, they began to want to customize the environment for a particular job in addition to customizing it for a user or group of users.

Release 7.45i Responds To User Requests

Now comes a change to the standard job creation features which allows specification of an environment name in the unibase.ini file which will be utilized for execution of that standard job.

Custom Env. Available In All Modes

In any of the keying modes for a batch, the environment changes specified in the section in the unibase.ini file identified by the environment name in the standard job is set before any mode (Entry, Resume, Verify, Examine, Correct, and Update) is entered. Upon completion of the batch, the mode is reset to what existed before the batch began.

Output Edit References Custom Env. Too

In an output edit run from a standard job, the environment changes occur at the start of the output edit and disappear at the end of the output edit.

Benefits Exist for Data Entry & Image Entry

Not only will this greatly benefit the setting of DMACI environment by image job, such environment variables as DENOSYNC can now be set by job.

Custom Keyboards Now Can Be By Job

Also this allows greater control over the keyboard by individual standard job.