Input
The job variables are always used by UDS/SQL in their entire length. Free areas are reserved for future extensions. Changes which are performed externally are consequently overwritten and should be avoided as they can result in undefined job variable contents.
Evaluation
In the case of automatic monitoring of individual statuses or changes to the content of an arbitrary item it must be borne in mind that changes can occur very rapidly one after the other. Under some circumstances it may therefore not be possible to intercept all the intermediary statuses.
The content of session and database job variables should not be used to check whether the processing routines are active. This information must be obtained from appropriate monitor job variables.
Malfunctions
Temporary malfunctions in supplying session or database job variables are reported once only the first time they occur.
If the DBH cannot assign a value to a job variable because a recoverable malfunction has occurred, message UDS0700 with the insert JOBV_SYSTEM_ERROR and return information (SEC-RC) is issued. The session is continued.
You can generally use HELP-MSG MSG-ID=JVSxxxx (xxxx=the last four characters of SEC-RC) to determine and possibly remove the cause of the malfunction.
When a permanent malfunction of the job variable subsystem is detected, message UDS0700 with the insert JOBV_PERMANENT_ERROR is issued. The session is continued.
Once a malfunction in an ongoing session has been removed, the session job variable is provided with the current value without any additional message the next time input is supplied. The same applies for the database job variable the next time the database is attached.