Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

SHOW-MAREN-STATUS Show status of MAREN

&pagelevel(4)&pagelevel

Privilege                 ADA, DA, administrator without domains

This statement provides an overview of MAREN’s current status. It displays information on the MAREN subsystem, the control task MARENCP, and the automatic free tape allocation facility MARENUCP. This information can also be called by all connected systems in the MAREN network.

DAs can only execute the statement in their own domain. The *ALL-FROM-DOMAIN specification is thus meaningless for them.

Format

SHOW-MAREN-STATUS                                                      Alias: SHMS
HOST-NAME = *OWN / *ALL / <alphanum-name 1..8> / *ALL-FROM-DOMAIN (...)

*ALL-FROM-DOMAIN


| DOMAIN = *STD-DOMAIN / *OWN / <alphanum-name 1..8>
,OVERFLOW-CONTROL = *BY-PROGRAM / *BY-SYSTEM

Operands

HOST-NAME =
System for which the MAREN status is to be displayed.

HOST-NAME = *OWN
Information is only output by the local system. If the ADA has used the MODIFY-ADMINISTRATION-SCOPE DOMAIN=... statement to become the DA of a domain, HOST=*OWN addresses the system which was determined by the HOST operand in the MODIFY-ADMINISTRATION-SCOPE statement.

HOST-NAME = *ALL
When domains are used, the information on all systems of the user’s own domain is output for the DA, and information on all systems for the ADA.

HOST-NAME = <alphanum-name 1..8>
Name of a system. If the DA enters the name of a system when domains are being used, this system must belong to the DA’s own domain.

HOST-NAME = *ALL-FROM-DOMAIN (...)
Information on the systems from specific domains is shown. This operand may only be used by the ADA.

DOMAIN =
Selects the domain.

DOMAIN = *STD-DOMAIN
Information on the systems of the standard domain is shown.

DOMAIN = *OWN
Information on the systems of the user’s own domain is shown. The user’s own domain is the domain of the system on which the ADA is currently working.

DOMAIN = <alphanum-name 1..8>
Information on the systems of the specified domain is shown.

OVERFLOW-CONTROL =
Type of screen overflow control in interactive mode.

OVERFLOW-CONTROL = *BY-PROGRAM
Control by the program: after an information block has been output, a message is displayed inquiring whether the current operation is to be continued or aborted.

OVERFLOW-CONTROL = *BY-SYSTEM
Control by BS2000: screen overflow control is based entirely on the system parameter TCHOFLO or the value set in the MODIFY-TERMINAL-OPTIONS command.

Notes

  • The following information is displayed for each system:

    • Name of the system.

    • TSN of the control task MARENCP.

    • TSN of the automatic free tape allocation facility MARENUCP.

    • Status of the MAREN catalog (FREE/LOCKED/UNLOCKED).

    • Transaction status of the subsystem (INACTIVE/ANNOUNCE/ACTIVE/FETCH).

    • TSN and archive number of the last transaction.

    • Name of the logging file.

    • Location Manager File (name of the reservation file) for MARENCP and MARENUCP.

    • Name of the exit module library for MARENCP and MARENUCP.

  • For information transfer in the network, active connections must exist between the system with the MAREN catalog and the other systems of the MAREN network. For this purpose, the HIPLEX MSCF subsystem must be loaded. The statement with the parameter HOST-NAME=*OWN works even if this requirements are not fulfilled.

Examples

Example 1: Status inquiry from the local system

//show-maren-status

=============================================================================
HOSTNAME MARENCP MARENUCP CATALOG    ===  TRANSACTION   ===   DOMAIN  SUB-SYS
           TSN     TSN    STATUS     STATUS   LA-TSN LA-VSN           VERSION
=============================================================================
LEIBNIZ4   5TAM    5TAX   UNLOCKED   INACTIVE  5TAX          HSMSTES<version>
-----------------------------------------------------------------------------
MAREN-CATALOG : :FSAU:$SYSMAREN.MARENCAT
%  MARM103 CONTINUE ACTION? REPLY (Y=YES; N=NO)?
Y
=============================================================================

HOST-NAME
LINK-NAME   EXIT#       FILE-NAME
=============================================================================
LEIBNIZ4
MARENLOG                :BUR7:$SYSMAREN.MAREN.LOGGING
MARENLMF/CP             :FSAU:$SYSMAREN.MARENLMF
MARENLMF/UCP            :FSAU:$SYSMAREN.MARENLMF
MARENLIB/CP (1,3,5)     :BUR7:$SYSMAREN.MARENLIB
MARENLIB/UCP(1,6)       :BUR7:$SYSMAREN.MARENLIB
%  MARM170 STATEMENT '//SHOW-MAREN-STATUS' PROCESSED

After an information block has been output, the message MARM103 is issued to inquire whether the operation is to be continued.

Example 2: Status inquiry from all systems in the MAREN network

//show-maren-status host=*all =============================================================================
HOSTNAME MARENCP MARENUCP CATALOG    ===  TRANSACTION   ===   DOMAIN  SUB-SYS
           TSN     TSN    STATUS     STATUS   LA-TSN LA-VSN           VERSION
=============================================================================
LEIBNIZ4   5TAM    5TAX   UNLOCKED   INACTIVE  5TDQ          HSMSTES<version>
D017ZE15   400J    400K   UNLOCKED   INACTIVE  41HT  QE3009  HSMSTES<version>
%  MARM197 ACCESS TO HOST 'D017ZE19' NOT POSSIBLE
D017ZE39   2B9I    2B91   UNLOCKED   INACTIVE  2RDX  QE0574  HSMSTES<version>
-----------------------------------------------------------------------------
MAREN-CATALOG : :FSAU:$SYSMAREN.MARENCAT.OS
=============================================================================
HOST-NAME
 LINK-NAME   EXIT#       FILE-NAME
=============================================================================
LEIBNIZ4
 MARENLOG                :BUR7:$SYSMAREN.MAREN.LOGGING
 MARENLMF/CP             :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLMF/UCP            :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLIB/CP  (1,3,5)    :BUR7:$SYSMAREN.MARENLIB
 MARENLIB/UCP (1,6)      :BUR7:$SYSMAREN.MARENLIB
D017ZE15
 MARENLOG                :SBZ7:$SYSMAREN.MAREN.LOGGING
 MARENLMF/CP             :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLMF/UCP            :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLIB/CP  (1,3,5)    :SBZ7:$SYSMAREN.MARENLIB
 MARENLIB/UCP (1,6)      :SBZ7:$SYSMAREN.MARENLIB
D017ZE39
 MARENLOG                :BU7B:$SYSMAREN.MAREN.LOGGING
 MARENLMF/CP             :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLMF/UCP            :FSAU:$SYSMAREN.MARENLMF.OS
 MARENLIB/CP  (1,3,5)    :BU7B:$SYSMAREN.MARENLIB
 MARENLIB/UCP (1,6)      :BU7B:$SYSMAREN.MARENLIB
%  MARM170 STATEMENT '//SHOW-MAREN-STATUS' PROCESSED


If the message MARM197 is output for a system, no further information is output for this system. If MARENCP-TSN or MARENUCP-TSN contains blanks, this means the program is not loaded on the system concerned. “CLOSED” is output after the file name of the MAREN catalog if the latter has been closed (at least) on the first system in the list using the CLOSE-MAREN-FILES statement. If MARENCP has been unloaded, the file name of the MAREN catalog is still output. It is possibly being accessed by other MAREN entities or other systems.