Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Administration of UDS/SQL via DCAM

&pagelevel(3)&pagelevel

If the DBH load parameter PP ADM=REMOTE is specified on starting the DBH, UDS/SQL opens a DCAM application. This enables the database administrator to set up a connection to UDS/SQL and enter database administrator commands from any data display terminal.

During the life of this connection the database administrator receives all UDS/SQL messages at this terminal.

Setting up the connection to UDS/SQL

You can set up a connection to the application confname on the BS2000 processor processor in a terminal emulation. If an administration password password1 is needed, you can pass it in the user message.

Connection via OMNIS is possible using the following command (see the OMNIS manual "Functions and Commands"):

O[PNCON] pac,PT=confname,PR=processor,TYP=DCAM[,CMSG|LMSG=password2]

confname

             

UDS/SQL configuration name; used as the DCAM application name. It consists of the first eight characters of the configuration name in the command:

/SET-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=configuration-name

processor


BCAM name of the host.

pac


Partner address code of the UDS/SQL configuration

MSG=password1 or

CMSG=password2 or

LMSG=password2



Password for administration via DCAM application. Must be specified only if a password has been defined by means of PP ADMPASS.

password1


A keyword with a length of one to four bytes

C’xxxx’:
One through four alphanumeric characters

X’nnnnnnnn’:
One through eight hexadecimal digits

password2


A keyword with a length of one to four bytes

xxxx 
One to four characters without a data type specification and unquoted. The password must not be specified in the C’...’ or X’...’ format since OMNIS does not interpret these characters as format identifiers but instead passes them on unchanged in the connection message. You should also note that the LCASE parameter in OPNCON currently has no effect and that lowercase characters in MSG or LMSG are always converted to uppercase. You may need to take account of these restrictions when assigning the administration password.

Once the connection has been established, UDS/SQL considers the data display terminal in question to be an administrator terminal. A connection request is rejected if the UDSADM program or another database administrator data display terminal is already connected to the configuration. It is also not possible to use the UDSADM program or the operator console to enter UDS/SQL commands while the database administrator’s data display terminal is connected via DCAM.

Once you have set up a connection to the DCAM application, you enter the command directly, i.e. without INFORM-PROGRAM or SEND-MSG:

dal-command
Pressing the [K1] key delays the sending of a UDS/SQL message by 20 seconds so that data entry is not disrupted.

Clearing the UDS/SQL connection

In order to cancel the connection to UDS/SQL, the database administrator uses the following command:

CLOSE ADMINSTRATION

The DCAM application is retained. It allows subsequent reconnection of any selected data display terminal or program.

UDS/SQL administration is performed via the local console as long as there is no existing connection via DCAM to UDS/SQL. The local console means the data display terminal on which commands are to be entered when load parameter PP ADM=LOCAL is specified, i.e.

  • the operator console if the master task is running as an ENTER job.

  • the data display terminal connected to the master task if the master task is running as an interactive job.

Logging administration data

If a data display terminal has set up a connection to UDS/SQL via DCAM, messages to and from UDS/SQL are also logged at the original console.

The original console is:

  • the operator console when the master task is running as an ENTER job.

  • the terminal connected to the task if the master task is running as an interactive job.

By means of the BS2000 command:

/MODIFY-JOB-OPTIONS logging=*par(listing=*yes)

and an appropriate assignment of the SYSLST file it is possible to store the logged data in a file.

You can use the PP UCON load parameter to define a console other than the original one as the output location for the logged data; see PP UCON in chapter "DBH load parameters".

Responses in error situations

If errors occur during UDS/SQL operation (e.g. line failure) or if termination of the DCAM application is enforced (e.g. with the network management command BCAPPL MODE=DEACTIVATE), UDS/SQL immediately tries to reopen the application. If the attempt fails, it is repeated every ten minutes. The database administrator can resume communication as soon as the application is reopened.

Messages concerning UDS/SQL DCAM administration

The DCAM administration status is logged at the local console by means of the following UDS/SQL message:

% UDS0347 UDS-ADMINISTRATION: ( s1) ( s2)

'BLANK's1

Description of the event

'BLANK's2:

UDS/SQL diagnosis insert

The following events are reported with the appropriate additional information:

  • opening of DCAM application with application name

  • connection setup with terminal name

  • connection cleardown with terminal name

  • connection abortion with feedback information

  • DCS abortion with feedback information

  • SVC error in the administration routine with name of macro and error status or feedback information.

More detailed information can be found in the manuals for “DCAM (BS2000)”.