HP 3000 Manuals HP 3000 Manuals
Session Processes and Job Processes Sessions and jobs are scheduled by two different types of processes. Sessions are run only from keyboard terminals. Jobs are run only from devices that send data to the system in batches or streams. Job processes do not support interactive or HOT devices (devices which do not spool or buffer data). The processes under which sessions and jobs are run are called JSMAIN. Every session or job requires an individual JSMAIN. Some of the characteristics of these processes, and the number available, are defined at the time the system is configured (using the SYSGEN utility, described in this manual). As far as users are concerned, the JSMAIN processes already exist and are ready for use. If more processes are required than have been defined, the system will automatically create them. After a job is scheduled, it waits its turn to be launched. Once launched, JSMAIN obtains the needed resources. If such resources are momentarily unavailable, the job is rescheduled. Occasionally a job may terminate due to an error. In such cases, the condition can be rectified by preceding the error causing command with the command CONTINUE. Usually, jobs are terminated by including the EOJ (End-of-Job) command at the end of the job stream. If a command in a jobstream is not immediately preceded by a CONTINUE command, or if the HPAUTOCONT variable has not been set to TRUE earlier in the jobstream, the job terminates when the command fails. Usually, sessions are terminated by entering the BYE command. Sessions also may be ended by a read timeout. A read timeout sets a limit on the length of time a session can last. The length of a timed read is set by redefining the HPTIMEOUT variable with the SETVAR command.