When managing pubsets, systems support can have the following functions monitored by job variables:
“Import pubset”
“Export pubset”
“Force pubset export”
When a shared pubset is imported, a job variable is created which indicates the availability of this pubset.
The following status values are set in a monitoring job variable during import and export of pubsets:
Value | Function | Meaning/reason for assigning the value |
$A | Export | Export aborted due to error or CANCEL-PUBSET-EXPORT command |
Import | Import aborted due to error | |
$E | Export | Export job successfully initiated |
$I | Import | Import job successfully initiated |
$R | Import | Pubset successfully imported |
$T | Export | Pubset successfully exported |
$W | Import | During import of a shared pubset the processor is waiting for the acknowledgment from the master |
Table 33: Status values when importing/exporting a monitoring job variable
In shared pubset operation within a multiprocessor network, a shared pubset-specific job variable is created on each home pubset of a sharer in order to monitor operations in the network. .
Value | Meaning/reason for assigning the value |
$R | Shared pubset available. |
$T | Shared pubset not available, e.g. due to failure of master. |
$A | Master switchover aborted due to error, e.g. failure of the master and unsuccessful declaration of a new master from the various slave processors. |
$C | Due to failure or shutdown of the master, a master switchover is performed on the public volume. |
Table 34: Monitoring job variables in shared-pubset mode
An overview of the commands in which systems support can monitor pubset management by means of job variables is presented in table 35 below.
For more information on pubset management, refer to the manuals “Introductory Guide to Systems Support” [
Notes on using a monitoring job variable
The job variable must not be write-protected.
If the job variable is not cataloged, message DMS0383 is output and the import/export job is executed without a monitoring job variable.
If the job variable is protected by a password, it can be declared as a monitoring job variable only if the user submitting the job has already entered the password in the password table (with ADD-PASSWORD) or specifies it in the JV-PASSWORD operand of the following commands.
Command | Operands relevant to monitoring of pubset management |
EXPORT-PUBSET | MONJV=*NONE/<filename 1..54 without-gen> JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479> |
Note on EXPORT-PUBSET: | |
FORCE-PUBSET-EXPORT | MONJV=*NONE/<filename 1..54 without-gen> JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479> |
IMPORT-PUBSET | MONJV=*NONE/<filename 1..54 without-gen> JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479> |
Note on IMPORT-PUBSET: Possible status values see table 34. |