Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Monitoring in pubset management

&pagelevel(3)&pagelevel

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.
Master switchover successfully completed.

$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
exports a previously imported pubset

MONJV=*NONE/<filename 1..54 without-gen>
defines the monitoring JV.

JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479>
defines a password for the monitoring JV.

Note on EXPORT-PUBSET:
The command generates a job that performs the pubset export. The pubset to be exported is set to “inaccessible”. The job waits until all jobs reserving resources have released their allocation (open files, or reservation of files with SECURE-RESOURCE-ALLOCATION). The export job returns information about the number of jobs still reserving the pubset. The task sequence numbers (TSNs) can be queried using the SHOW-PUBSET-PARAMETER command. Following termination of the wait state the user catalog is closed and all resources are released. Messages generated by the job are output at the operator terminal. The wait state during export processing can be terminated with the operand TERMINATE-JOBS=YES. This causes all jobs still occupying resources to be terminated in an orderly manner. If the wait state cannot be exited, this can be enforced by means of the FORCE-CATALOG-EXPORT command.
The change in availability is reported to all active processors of the multiprocessor network. The export job can be monitored by means of a job variable (see MONJV). Conditional job control (CJC) can be used to respond to the various processing states.

FORCE-PUBSET-EXPORT
forces export of a pubset.

MONJV=*NONE/<filename 1..54 without-gen>
defines the monitoring JV.

JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479>
defines a password for the monitoring JV.

IMPORT-PUBSET
imports a pubset.

MONJV=*NONE/<filename 1..54 without-gen>
defines the monitoring JV.

JV-PASSWORD=NONE/<c-string 1..4>/<x-string 1..8>/ <integer -2147483648..21484836479>
defines a password for the monitoring JV.

Note on IMPORT-PUBSET:
The import job can be monitored using a job variable (see MONJV). Conditional job control (CJC) can be used to respond to the various processing states.
If a shareable pubset was imported, its availability is additionally logged in a separate job variable.
During the import process this is reset or created as a new job variable on the home pubset of the importing processor: The default name is
:<cat-id home>:$TSOS.SYS.PVS.<cat-id shared-pubset>.MASTER.CONTROL

Possible status values see table 34.