Session job variable

The DBH supports a session job variable that helps to automate administration. This job variable can be used to control user jobs and programs.

The following job variable is supplied by UDS/SQL:

UDSSQL.DBH.session

session

is the variable part of the job variable name. The first eight characters of the full configuration-name is used as the default value. If desired, the database administrator can also define some other name for session before starting the DBH in the master task or in the linked-in task by using the following command:
/SET-FILE-LINK LINK-NAME=UDSDBHJV,FILE-NAME=session

If the job variable UDSSQL.DBH.session does not exist, it is created with the following attributes:

ACCESS=WRITE
SHARE=YES
BASACL_NONE (standard access control)

If the job variable is to be used with other properties, you must create it with the required properties before the DBH starts or before the utility routine executes. When using job variables, access control can be implemented using standard resources (e.g. Basic-ACL, Guards).

Before a job variable is used in a foreign user ID, you must either create it yourself or take appropriate measures (e.g. co-ownership in a foreign user ID) to ensure that it can be created dynamically.

Please also take note of “Information on using the job variables”.

The job variable UDSSQL.DBH.session is structured as follows:

Column	Contents	Meaning
1-30	UDSDBH_STARTING / UDSDBH_ACTIVE / UDSDBH_CLOSE_INITIATED / UDSDBH_NORMAL_END / UDSDBH_ABNORMAL_END	Status (1)
		DBH start (2)
31-40	yyyy-mm-dd	Date
41-48	hh:mm:ss	Time
		DBH end (3)
49-58	yyyy-mm-dd	Date
59-66	hh:mm:ss	Time
67-68	01	Version ID of the layout of the session job variable
69-76	session-name	Configuration name of the DBH session
77-84	host	Host of the DBH session
85-92	nnnnnnnn / 'BLANK'	Session section number (4)
93		Status of the DBH operational interruption:
	B /	– Current operational interruption
	'BLANK'	– Currently no operational interruption
94-96		Type of current or last DBH operational interruption (5)
	DAL /	– Because of DALs (PERFORM)
	DBH /	– Because of internal system activities
	'BLANK'	– No operational interruption has occurred as yet
97		Attaching database or realm in current or last operational interruption (5)
	A /	– Yes
	– /	– No
	'BLANK'	– No operational interruption has occurred as yet
98		Detaching database or realm in current or last operational interruption (5)
	D /	– Yes
	– /	– No
	'BLANK'	– No operational interruption has occurred as yet
99		Activity with respect to ALOG files in current or last operational interruption (5)
	A /	– Yes
	– /	– No
	'BLANK'	– No operational interruption has occurred as yet
100		Activity with respect to RLOG files in current or last operational interruption (5)
	R /	– Yes
	– /	– No
	'BLANK'	– No operational interruption has occurred as yet
101-112	'BLANK'	Reserved
		Start of the preparatory phase for the current or last operational interruption (5)
113-122	yyyy-mm-dd	Date
123-130	hh:mm:ss	Time
131-138	hh:mm:ss	Start of the Implementation phase for the current or last operational interruption (5) Time
139-146	hh:mm:ss	End of the last operational interruption (5) Time
147-162	'BLANK'	Reserved
		Last change to the job variable
163-172	yyyy-mm-dd	Date
173-180	hh:mm:ss	Time

Table 24: Structure of the session job variable for UDS/SQL

Comments

(1)

Status

Content	Set when?
UDSDBH_STARTING	When the DBH starts
UDSDBH_ACTIVE	After successful initialization (e.g. System Ready message of the independent DBH)
UDSDBH_CLOSE_INITIATED	When no further requests are permitted in the DBH because the DBH end has been initiated by the UDS/SQL administration or for internal reasons by the DBH
UDSDBH_NORMAL_END / UDSDBH_ABNORMAL_END	When the DBH ends

(2)

DBH start is initialized with 0 when the DBH starts and is filled with the current time following successful initialization (e.g. System Ready message of the independent DBH).

(3)

DBH end is initialized with 0 when the DBH starts and is filled with the current time when the DBH ends.

(4)

Session section number is initialized with blanks when the DBH starts and during initialization is filled with a value which unambiguously identifies the session section and remains unchanged up to the end of the session section.

The session section number enables the assignment of database job variables to a current session to be checked: only if the session section numbers in the database job variables and in the session job variables match are the contents of the database job variables valid for the current session.

(5)

The displays for and times of the various phases of an operational interruption always relate to the current or last operational interruption displayed in Status of the DBH operational interruption (byte 93).

Internal operational interruptions in the DBH’s start or termination phase are not displayed.