Required files
GUARDS subsystem
File
Name of file
Subsystem catalog
$TSOS.SYSSSC.GUARDS.nnn
Subsystem library
... for SU /390 and S servers
$TSOS.SYSLNK.GUARDS.nnn
... for SU x86 and SQ servers
$TSOS.SKMLNK.GUARDS.nnn
Macro library
$TSOS.SYSLIB.GUARDS.nnn
Syntax file
$TSOS.SYSSDF.GUARDS.nnn
Message file
$TSOS.SYSMES.GUARDS.nnn
REP file
$TSOS.SYSRMS.GUARDS.nnn
IMON file
$TSOS.SYSSII.GUARDS.nnn
SSINFO file
$TSOS.SYSSSI.GUARDS.nnn
Table 11: Installation files for GUARDS (nnn = version of subsystem)
GUARDDEF subsystem
File
Name of file
Subsystem catalog
$TSOS.SYSSSC.GUARDDEF.nnn
Subsystem library
... for SU /390 and S servers
$TSOS.SYSLNK.GUARDDEF.nnn
... for SU x86 and SQ servers
$TSOS.SKMLNK.GUARDDEF.nnn
Macro library
$TSOS.SYSLIB.GUARDDEF.nnn
Syntax file
$TSOS.SYSSDF.GUARDDEF.nnn
Message file
$TSOS.SYSMES.GUARDDEF.nnn
REP file
$TSOS.SYSREP.GUARDDEF.nnn
IMON file
$TSOS.SYSSII.GUARDDEF.nnn
Table 12: Installation files for GUARDDEF (nnn = version of subsystem)
GUARDCOO subsystem
File
Name of file
Subsystem catalog
$TSOS.SYSSSC.GUARDCOO.nnn
Subsystem library
for SU /390 and S servers
$TSOS.SYSLNK.GUARDCOO.nnn
for SU x86 and SQ servers
$TSOS.SKMLNK.GUARDCOO.nnn
Macro library
$TSOS.SYSLIB.GUARDCOO.nnn
Syntax file
$TSOS.SYSSDF.GUARDCOO.nnn
Message file
$TSOS.SYSMES.GUARDCOO.nnn
REP file
$TSOS.SYSREP.GUARDCOO.nnn
IMON file
$TSOS.SYSSII.GUARDCOO.nnn
Table 13: Installation files for GUARDCOO (nnn = version of subsystem)
The following files are required for installation:
- Subsystem catalog
This contains the description of the subsystem from the viewpoint of DSSM.
Subsystem library
This contains the prelinked module with the name GUARDS, GUARDDEF or GUARDCOO.SDF syntax file
This contains the description of the command syntax for the corresponding subsystem.Message file
The message file contains the messages for the corresponding subsystem.REP file
The REP file contains corrections to be applied during start of subsystem. If no corrections exist, the file is empty.
SSINFO file (optional, only for GUARDS subsystem)
It can be specified in the SSINFO file how many pubsets (i.e. how many GUARDS catalogs) are administered by a GUARDS server task.
Details on the SSINFO file can be found in section "SSINFO file".
Notes
If the name of an SSINFO file is specified in the subsystem catalog, this file must exist when the subsystem is started; otherwise, the load operation is aborted by DSSM.
Error during GUARDS subsystem initialization
Symptom:
Loading of the subsystem is aborted with error message PRO6007.
Effects:
In this session, GUARDS responds to all inquiries from object management systems with a negative response.
Reasons:
Error message PRO6007 includes information about the error class. The precise reason can be determined from the SERSLOG entry:
01: | Error when requesting the task lock. |
02: | Error when signing the subsystem into task administration. |
03: | Error when reading the home pubset. |
04: | Error determining the hardware basis on which the BS2000 version is running (x86). |
05: | Error determining the active BS2000 version. |
06: | Error when signing in the condition administration. |
Error during initialization of the GUARDS administration
Symptom:
Initialization of the GUARDS administration for a pubset is aborted with error message PRO6002.
Effects:
Initialization of the GUARDS administration for a pubset starts IMPORT-PUBSET processing. If an error occurs, the operator is informed via message PRO6002 and is asked whether IMPORT-PUBSET processing is to be continued without the GUARDS administration. If the operator responds with YES, GUARDS returns a negative response to all inquiries from object management systems during this session.
Reasons:
Error message PRO6002 includes information about the error class. The precise reason can be determined from the SERSLOG entry:
01: | The task lock for access to subsystem-specific global tables could not be set or released. |
02: | The pubset table could not be created, found or chained. |
03: | Error when checking the guards catalogs $TSOS.SYSCAT.GUARDS. |
/01: The file is not a guards catalog. | |
04: | Error when creating the server task or when establishing a connection to the |
/01: Parameter error | |
05: | Error when opening the guards catalog; if a DMS error occurred, the DMS error code is also output. |
06: | Internal error when establishing a connection. |
Remedy:
If the error occurred during IMPORT-PUBSET processing, abort execution and initiate
IMPORT-PUBSET processing again.
If the reason was 03, check whether there is a file with the name
$TSOS.SYSCAT.GUARDS which is not a guards catalog. If so, rename this file.
Abnormal termination of a GUARDS server task
The guards catalog is accessed via a server task. If a server task fails, the global tables are cleaned up and the GUARDS administration for the pubsets served by this server task is terminated abnormally. This is documented with error message PRO6006 on the console.
Symptom:
A server task is aborted with error message PRO6006.
Effects:
GUARDS returns a negative response to all inquiries from object management systems in this session.
Reasons:
The reason can be determined only by analysis of the system dump. Please inform your system service personnel.
Remedy:
There are two possibilities:
01: | Export the pubset and then import it again. |
02: | Use the administration command /REPAIR-GUARD-FILE to activate administration of the guards catalog for the pubset. |
SERSLOG entries
If an interface call returns an unexpected error code, or if an internal error occurs, a SERSLOG entry is written.
The following entries may be written:
GUARDS subsystem
PRO0001: Parameter error, interface error
Entry format:
PARAMETERAREA ERROR. CALLED INTERFACE: 1
PARAMETERAREA: 2
ADDRESS OF CALLER: 31: Name of the faulty interface (8 bytes)
2: Parameter area of the interface (variable)
3: Caller’s name and address (printable) (22 bytes)PRO0002: Internal error
Entry format:
INTERNAL ERROR IN MODULE: 1 (2).
REASON: 3 4
ADDRESS OF CALLER: 51: Name of the module (8 bytes)
2: Module-internal error number (2 bytes)
3: Brief description of the error (80 bytes)
4: Data area (variable)
5: Caller’s name and address (printable) (22 bytes)
If a SERSLOG entry is written with the option DUMP=DIAG, error message PRO6008 is also output on the console.
Subsystem GUARDDEF
DEF0001: Parameter error, interface error
Entry format:
PARAMETERAREA ERROR. CALLED INTERFACE: 1
PARAMETERAREA: 2
ADDRESS OF CALLER: 31: Name of the faulty interface (8 bytes)
2: Parameter area of the interface (variable)
3: Caller’s name and address (printable) (22 bytes)DEF0002: Internal error
Entry format:
INTERNAL ERROR IN MODUL: 1 ( 2).
REASON: 3 4
ADDRESS OF CALLER: 51: Name of the module (8 bytes)
2: Module-internal error number (2 bytes)
3: Brief description of the error (80 bytes)
4: Data area (variable)
5: Caller’s name and address (printable) (22 bytes)
If a SERSLOG entry is written with the option DUMP=DIAG, error message DEF5002 is also output on the console.
Subsystem GUARDCOO
COO0001: Parameter error, interface error
Entry format:
PARAMETERAREA ERROR. CALLED INTERFACE: 1
PARAMETERAREA: 2
ADDRESS OF CALLER: 31: Name of the faulty interface (8 bytes)
2: Parameter area of the interface (variable)
3: Caller’s name and address (printable) (22 bytes)COO0002: Internal error
Entry format:
INTERNAL ERROR IN MODUL: 1 ( 2).
REASON: 3 4
ADDRESS OF CALLER: 51: Name of the module (8 bytes)
2: Module-internal error number (2 bytes)
3: Brief description of the error (80 bytes)
4: Data area (variable)
5: Caller’s name and address (printable) (22 bytes)
If a SERSLOG entry is written with the option DUMP=DIAG, error message COO5002 is also output on the console.