Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Command sequence for starting and operating UDSMON

&pagelevel(3)&pagelevel

01  [/CREATE-FILE FILE-NAME=monitor-file
      [,SUPPORT=*PUBLIC-DISK(SPACE=*RELATIVE(PRIMARY-ALLOCATION=primary - 
       ,SECONDARY-ALLOCATION=secondary)) or
       ,SUPPORT=*PRIVATE-DISK(VOLUME=priv-vsn,DEVICE-TYPE=device[,SPACE=...])]]
    [/ADD-FILE-LINK LINK-NAME=TR,FILE-NAME=monitor-file,ACCESS-METHOD=*SAM]
02  /START-UDS-MONITOR
03  "udsmon statements for starting"
04 EM, DUE
05 "udsmon commands during execution"
06 EM, DUE
07 /INFORM-PROGRAM MSG='END'

Explanation

01        

If the monitor file is to be set up explicitly, the CREATE-FILE command must be used for this purpose. In this case specifying :catid: is permitted in accordance with BS2000 conventions (see section “Using pubsets in UDS/SQL”).

02

The monitor is started.

04/06

An interrupt during monitor execution is initiated by means of EM, DUE.

07

The monitor is terminated.

After a program interrupt, due to [K2] for example, the INFORM-PROGRAM command is required in order to resume operation.

In batch mode, an invalid UDSMON statement causes the monitor start to be terminated. An error message is output to SYSOUT.