CA Common Logger Address Space

The CA Common Logger service runs as a CAMASTER-managed address space, based on the Common Address Space (CASRV) address space shell technology, which interfaces with the z/OS Logger and manages the allocated z/OS log streams. This component also provides a command statement external interface to dynamically manage individual log streams.
ccsfzos15
The CA Common Logger service runs as a CAMASTER-managed address space. The service is based on the Common Address Space (CASRV) address space shell technology, which interfaces with the z/OS Logger and manages the allocated z/OS log streams. This component also provides a command statement external interface to dynamically manage individual log streams.
2
2
Logger Operational Overview
The CAMASTER component creates and manages the CA Common Logger address space named CALOGGER. The CAMASTER component can start the CALOGGER address space automatically during early IPL initialization of CA components. No action is required on the part of the installation to update JCL PROCs, establish automation rules, or update z/OS Workload Manager policy. The installation defines a security subsystem user ID for the CALOGGER address space.
To start the CALOGGER address space at IPL, code statements in an optional CAIMST20 logical PARMLIB member. Use the following syntax for the CAIMST20 PARMLIB member statement:
COMPONENT (CALOGGER), /* CA Common Logger */ START=YES /* Start at IPL */
To query the status of the CALOGGER address space:
F CAMASTER,DISPLAY COMPONENTS
To start the CALOGGER address space when it is not active:
F CAMASTER,START COMPONENT=CALOGGER[,SRVPARM(REINIT)]
The optional SRVPARM keyword
REINIT
initiates a Cold Start of the CALOGGER address space.
Cold Start Background
Requesting a cold start causes CA Common Logger to reload its persistent data structure (LGCAREA) that resides in common storage. The reload process resets CA Common Logger to its initial state by deleting all connections. A cold start is requested because of an unrecoverable, fatal error with a connection or log device control block chain or function vector that prevented CA Common Logger from Warm Starting. This scenario may occur when CA Logger can warm start, and it exhibits unexpected, invalid, or uncorrectable behavior.
Cold starting does not free the LGCAREA or run the control block chains and free their storage. Doing so may trigger an abend and may prevent CA Logger from initiating. The storage is abandoned (orphaned) and a new LGCAREA is loaded and used for new processing. Because of the lost storage, use cold start only when a warm start fails or when CA Logger experiences repeated abnormal termination.
z/OS Logstreams
The CA Common Logger component uses z/OS logstreams, which you define using the IBM utility IXCMIAPU.
CALOGGER Command Reference
Commands can be entered using the z/OS Modify command or can be processed during CALOGGER initialization using the
CAILGR00
parmlib member.
ADD Command
The ADD [LOGGER] command defines a log for use by the CALOGGER address space.
ADD[LOGGER]LOGDEVICE[LOGNAME=
logname
][PRODUCT=
product
][DESCRIPTION=
description
][LSNAME=
lsname
][LOGCLASS=
logclass
]
  • LOGNAME
    Specifies a 1- through 16-character name of the log.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character may be uppercase alphabetic, numeric, national, or an underscore ‘_’. The log name is the method by which a CA product references a CALOGGER-managed log.
  • PRODUCT
    Specifies a 1- through 24-character mask of a CA product or component. A log stream may be dedicated to given CA products or components when this operand is specified.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character may be uppercase alphabetic, numeric, national, a dash ‘-‘or an underscore ‘_’.
    Two mask characters are supported. A question mark ‘?’ matches any single character. An asterisk ‘*’ matches the current character position and any subsequent characters.
  • DESCRIPTION
    Specifies a 1- though 64-character quoted text string that provides a description of the log.
  • LSNAME
    Specifies a 1- through 26-character name of a previously defined z/OS Logger log stream. The name must follow the naming convention that is established for z/OS log streams.
  • LOGCLASS
    (Optional) Specifies the classification of acceptable data objects that make up the content on this log stream. The operand value corresponds to the LOGCLASS= specification on the #LOGGER programmable interface.
    The LOGCLASS operand must be one of the following keycodes: DATA, MSG, TRACE, ANY.
    Default
    : ANY
DISPLAY USERS Command
This command displays information about the active users who are registered to CA Common Logger.
DISPLAY [LOGGER] USERS [SUMMARY|DETAILED] [LOGNAME=
logname
][PRODUCT=
product
]
  • USERS
    Displays information about the active user connections.
  • SUMMARY|DETAILED
    (Optional) Specifies whether the DISPLAY command shows general information about each user (SUMMARY) or whether the DISPLAY shows additional information for the CA product connections (DETAILED).
    Default
    : SUMMARY
  • LOGNAME
    (Optional) Specifies a 1- through 16-character logname mask.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character can be uppercase alphabetic, numeric, national, or an underscore ‘_’. The masking of log names is supported. A question mark (‘?’) matches a single character position. An asterisk matches the current character position and all following positions.
    Default
    : “*” (display all defined logs)
  • PRODUCT
    (Optional) Specifies a 1- through 24-character mask of a CA product or component. A log stream can be dedicated to given CA products or components if this operand is specified.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character can be uppercase alphabetic, numeric, national, a dash ‘-‘or an underscore ‘_’.
    Two mask characters are supported. A question mark ‘?’ matches any single character. An asterisk ‘*’ matches the current character position and any subsequent characters.
    The two mask characters operate as follows. A question mark ‘?’ matches any single character while an asterisk ‘*’ matches the current character position and any subsequent characters. The masking of the PRODUCT name lets you share a given log device between multiple CA products.
    Default
    : “*” (any CA product or component can write data objects to this log stream)
Example Output: SUMMARY (default)
CASV0104I 14.08.57 DISPLAY 482 482 Registered product Log device name job name Job Id Persist CA8 $CA8_LOG_RECORDS FISJA01A J0000067 Job step CA8 $CA8_LOG_RECORDS FISJA01B J0000068 Task CA8 $CA8_LOG_RECORDS FISJA01B J0000068 Task CA9 CA9_LOG_RECORDS FISJA01B J0000068 Task CA9 CA9_LOG_RECORDS FISJA01B J0000068 Task
Example Output: DETAILED
CASV0104I 14.09.11 DISPLAY 487 487 Registered product Log device name job name Job Id Persist CA8 $CA8_LOG_RECORDS FISJA01A J0000067 Job step Component = Release = v14r01 Instance = Access = UPDATE CA8 $CA8_LOG_RECORDS FISJA01B J0000068 Task Component = Release = v14r01 Instance = Access = UPDATE CA8 $CA8_LOG_RECORDS FISJA01B J0000068 Task Component = Release = v14r01 Instance = Access = (UPDATE,RETRIEVE) CA9 CA9_LOG_RECORDS FISJA01B J0000068 Task Component = Release = v14r01 Instance = Access = RETRIEVE CA9 CA9_LOG_RECORDS FISJA01B J0000068 Task Component = Release = v14r01 Instance = Access = UPDATE
DISPLAY LOGDEVICES Command
This command displays log device data.
DISPLAY[LOGGER] LOGDEVICES [SUMMARY|DETAILED|USERS] [LOGNAME=
logname
][PRODUCT=
product
]
  • SUMMARY|DETAILED|USERS
    (Optional) Specifies whether the DISPLAY shows summary information about all LOGDEVICEs (SUMMARY), detailed information about all LOGDEVICEs (DETAILED) or summary information about all LOGDEVICEs and the users that have registered connections to the LOGDEVICEs (USERS).
    Default
    : SUMMARY
  • LOGNAME
    (Optional) Specifies a 1- through 16-character logname mask.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character may be uppercase alphabetic, numeric, national, or an underscore ‘_’. Masking of log names is supported. A question mark (‘?’) matches a single character position. An asterisk matches the current character position and all following positions.
    Default
    : “*” (display all defined logs)
  • PRODUCT
    (Optional) Specifies a 1- through 24-character mask of a CA product or component. A log stream may be dedicated to given CA products or components if this operand is specified.
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character may be uppercase alphabetic, numeric, national, a dash ‘-‘or an underscore ‘_’.
    Two mask characters are supported. A question mark ‘?’ matches any single character. An asterisk ‘*’ matches the current character position and any subsequent characters.
    Default
    : “*” (any CA product or component may write data objects to this log stream)
Example Output: SUMMARY
CASV0104I 14.09.33 DISPLAY 491 491 LOGNAME PRODUCT STATE $CA8_LOG_RECORDS CA8 CONNECTED CA9_LOG_RECORDS CA9* CONNECTED
Example Output: DETAILED
CASV0104I 14.09.45 DISPLAY 494 494 LOGNAME PRODUCT STATE $CA8_LOG_RECORDS CA8 CONNECTED CA8 LOG STREAM LSName=FISJA01A Maxbuffer Size= 65532 LogType=z/OS Log Stream class="Data" CA9_LOG_RECORDS CA9* CONNECTED CA9 LOG STREAM LSName=FISJA01B Maxbuffer Size= 65532 LogType=z/OS Log Stream class="Data"
Example Output: USERS
CASV0104I 14.09.57 DISPLAY 516 516 LOGNAME PRODUCT STATE REGISTERED_PRODUCT JOBNAME ASID TCB $CA8_LOG_RECORDS CA8 CONNECTED CA8 FISJA01A 001C 006F8030 CA8 FISJA01B 0031 006FF168 CA8 FISJA01B 0031 006D09A8 CA9_LOG_RECORDS CA9* CONNECTED CA9 FISJA01B 0031 006FF168 CA9 FISJA01B 0031 006D09A8
REMOVE Command
The REMOVE [LOGGER] command deletes a log from use by the CALOGGER address space.
REMOVE[LOGGER]LOGDEVICE[LOGNAME=
logname
][PRODUCT=
product
][FORCE=NO|YES]
  • LOGNAME
    Specifies a 1- through 16-character name of the log
    The first character must be uppercase alphabetic or national (‘@’,’#’,’$’). Any subsequent character may be uppercase alphabetic, numeric, national, or an underscore ‘_’. The log name must reference a log that is actively being managed by the CA Logger address space.
  • PRODUCT
    Specifies a 1- through 24 character mask of a CA product or component. The first character must be uppercase alphabetic or the mask characters, asterisk (‘*’) or question mark (‘?’). Any subsequent character may be uppercase alphabetic, numeric, national (‘@’,’#’,’$’), a dash ‘-‘, an underscore ‘_’, or the mask characters, an asterisk (‘*’), or a question mark (‘?’).
    The PRODUCT name operand is not used as a mask on the REMOVE command, but, is used to search for an exact match against a log device that has a PRODUCT name that is defined with mask characters.
  • FORCE
    (Optional).
    Controls whether the log device can be removed, even though there are active users of the log device.
  • NO
    If there are active connections to the log device, the REMOVE command is ignored with an appropriate command response.
  • YES
    Even if there are active connections to the log device, this setting permits the removal of a log device. Only specify YES under the recommendation of Broadcom Support.
    Default
    : NO
Example: Issue a command using z/OS Modify
The following example illustrates how to issue a command using z/OS Modify:
F CALOGGER,ADD LOGDEVICE,LOGNAME=CA_PRODUCT_LOG,DESCRIPTION=MYSAMP.DASD.STG1,LSNAME=MY.LOG4,PROD=CA_PRODUCT_NAME
CAILGR00 Logical Parmlib Member
During the startup process, the CA Common Logger Address Space searches for the logical PARMLIB member named
CAILGR00
. The member lets CA Common Logger automatically execute the CA Common Logger commands that were defined in the CAILGR00 PARMLIB member.
Consider the following best practices:
  • Add the log streams dynamically to CA Common Logger using the ADD LOGDEVICE command. After you add the log streams, you can define the log streams permanently by placing the ADD LOGDEVICE command in the
    CAILGR00
    PARMLIB member.
  • In a sysplex, run the CA Common Logger Address Space on all system images that are contained in the sysplex. With this practice, CA Common Logger can process commands on system-oriented, DASD-only log streams and sysplex-wide, coupling-based log streams. When the sysplex uses a shared PARMLIB for all systems, you can specify one CAILGR00 PARMLIB member for all the systems. The following examples describe the syntax that is required for a PARMLIB (system-unique) and a shared PARMLIB:
    Example: PARMLIB
    /*********************************************************************/ /* */ /* SYS1.PARMLIB(CAILGR00): CA COMMON LOGGER */ /* */ /* CALOGGER COMPONENT CONFIGURATION PARAMETERS */ /* */ /*********************************************************************/ /*-------------------------------------------------------------------*/ /* SET CASERV CONTROL PROGRAM PARAMETERS */ /*-------------------------------------------------------------------*/ SET DAE=YES /* SUPPRESS DUPLICATE SVC DUMPS */ /*-------------------------------------------------------------------*/ /* SYSPLEX CF LOG STREAM FOR CA7 */ /*-------------------------------------------------------------------*/ ADD LOGDEV LOGNAME=CA7_LOG_RECORDS, /* CA7 LOG RECORDS */ LSNAME=CA7.LOG.RECORDS, /* Z/OS LOG STREAM NAME */ PRODUCT(CA7), DESCRIPTION('CA7 LOG RECORDS') /*-------------------------------------------------------------------*/ /* DISPLAY THE MANAGED LOG DEVICES */ /*-------------------------------------------------------------------*/ DISPLAY LOGDEV /* DISPLAY MANAGED LOG DEVICES */
    Example: Shared PARMLIB
    /*********************************************************************/ /* */ /* SYS1.PARMLIB(CAILGR00): CA COMMON LOGGER */ /* */ /* CALOGGER COMPONENT CONFIGURATION PARAMETERS */ /* */ /*********************************************************************/ /*-------------------------------------------------------------------*/ /* SET CASERV CONTROL PROGRAM PARAMETERS */ /*-------------------------------------------------------------------*/ IF &SYSNAME. = (XE47) SET DAE=YES /* SUPPRESS DUPLICATE SVC DUMPS */ ENDIF /*-------------------------------------------------------------------*/ /* SYSPLEX CF LOG STREAM FOR CA7 */ /*-------------------------------------------------------------------*/ ADD LOGDEV LOGNAME=CA7_LOG_RECORDS1, /* CA7 LOG RECORDS */ LSNAME=CA7.&SYSPLEX..LOG.RECORDS, /*Z/OS LOGSTREAM NAME */ PRODUCT(CA7), DESCRIPTION('CA7 SYSPLEX-WIDE LOG RECORDS') /*-------------------------------------------------------------------*/ /* DASD ONLY LOG STREAM FOR CA7 LOCAL SYSTEM RECORDS */ /*-------------------------------------------------------------------*/ ADD LOGDEV LOGNAME=CA7_LOG_RECORDS2, /* CA7 LOG RECORDS */ LSNAME=CA7.&SYSNAME..LOG.RECORDS, /*Z/OS LOGSTREAM NAME*/ PRODUCT(CA7), LOGCLASS=DATA, DESCRIPTION('CA7 SYSTEM LEVEL LOG RECORDS') /*-------------------------------------------------------------------*/ /* DISPLAY THE MANAGED LOG DEVICES */ /*-------------------------------------------------------------------*/ DISPLAY LOGDEV /* DISPLAY MANAGED LOG DEVICES */
With the
CAILGR00
member, you can specify any of the commands that are supported by the CA Common Logger Address Space and the CA Common Address Space shell.
CA Logger Unload Utility
The CA Common Logger service supports an unload utility that archives and deletes data objects from a log stream. When you execute the utility, it unloads all records from a given log stream and then deletes the records.
For example, a system administrator or system programmer might run the utility when a log is close to full or to clean up the log file to make room for more records.
The utility can also unload data from a log stream that is used as a staging area to a sequential data set (most likely a generation data group (GDG)) and delete the offloaded data objects.
Example:
An example of a
CALGUNLD
member JCL can be found in the
CAW0JCL
dataset.
The example presumes that two different releases of the product are in use. The log records from release 14.1 are written to the archive of all records and also isolated into their own archive. This scenario presumes that the product includes the release number in the metadata for each log record. OUTDD parameter statements are used to control which log records are written to the specified DD statements.
Unloaded log records are written to DDNAME ALLRECS and only records related to release v14.1 are written to DDNAME V141RECS.
The output files that hold the log records are next generations in two GDGs.
Unload Implementation Considerations
The control statements are grouped, with each group beginning with an OPTIONS record followed by zero or more OUTDD statements. Each record in a group is read and parsed. After all records in a group have been parsed, the information is verified and if all edits pass, control passes to the UNLOAD routine.
The UNLOAD routine then performs the following actions:
  • Connects to the log device that is defined in the OPTIONS record
  • Opens all files that are defined in the OUTDD statements
  • Writes the control record
  • Loops, reading all log records and checking each OUTDD to see if the log record matches the selection criteria for that OUTDD.
When all log records have been processed, all output files are closed, and the log records are purged from the log file.
Unload Security Considerations
The CA Logger Unload utility can delete log records from the log stream; therefore, the security administrator should control who can execute this utility. If your site does not have security profiles in place that limit access to the Unload utility, everyone can execute it.
When the Unload utility starts, it performs a security check to determine if the person running the utility has the highest security access to the class FACILITY and the resource CALOGGER.CALGUNLD. If the security check fails, the utility terminates with message
CALG9047E
.
To provide the appropriate access level, a security administrator must issue one of the following commands to authorize a user to run the Unload utility.
The following commands assume that the resource classes and resources are defined to the security product.
CA ACF2
SET RESOURCE(FAC) RECKEY CALOGGER ADD(CALGUNLD UID(
UID string for user
) ALLOW)
CA Top Secret
TSS PERM(
user
) IBMFAC(CALOGGER.CALGUNLD) ACCESS(ALL)
IBM RACF
RDEFINE FACILITY (CALOGGER.CALGUNLD) UACC(NONE) PERMIT CALOGGER.CALGUNLD CLASS(FACILITY) ID(
user
) ACCESS(ALTER)
Unload Utility JCL
Use this JCL to execute this utility:
//SYSPRINT DD SYSOUT=* //anyddn1 DD DSN=
dsname
,DISP=[
disp1
[
disp2
[
disp3
]], // UNIT=
unitinformation
,SPACE=
spaceinformation
, // DCB=(LRECL=
lrecl
,BLKSIZE=
blksize
,RECFM=
recfm
) //anyddn2 DD DSN=
dsname
,DISP=[
disp1
[
disp2
[
disp3
]], // UNIT=
unitinformation
,SPACE=
spaceinformation
, // DCB=(LRECL=
lrecl
,BLKSIZE=
blksize
,RECFM=
recfm
) … //anyddnn DD DSN=
dsname
,DISP=[
disp1
[
disp2
[
disp3
]], // UNIT=
unitinformation
,SPACE=
spaceinformation
, // DCB=(LRECL=lrecl,
BLKSIZE
=
blksize
,RECFM=
recfm
) //SYSIN DD * control statements
  • anydd
    n
    :
    Specifies a valid DDNAME. The name is used in the DDNAME parameters of the OUTDD statement. These files can be any logical record length, blocksize, and record format. The LRECL must be large enough to allow writing of the longest possible log record. If the LRECL is too small, the CALGUNLD utility abends. The record format can be fixed, variable, or undefined.
  • dsname
    :
    Specifies the data set name that is associated with the unload activity.
  • disp1
    :
    Specifies how the file should be allocated to you:
    • SHR:
      Allocates an existing data set non-exclusively.
    • OLD:
      Allocates an existing data set for the exclusive use of the CALGUNLD utility.
    • NEW
      Allocates a new data set that does not already exist.
    • MOD:
      Allocates a new or existing data set for the exclusive use of the CALGUNLD utility. The "write pointer" is positioned to the end of the data set so that you may extend the data set with more records.
  • disp2
    :
    Specifies what should be done with the data set when it is deallocated normally:
    • KEEP:
      Keep it, but do not catalog it. KEEP is the default value if it was an existing data set that was allocated.
    • DELETE
      Delete it. If the data set was allocated through the catalog (without specification of volume serial number), it is uncatalogued. DELETE is the default for a newly allocated data set.
    • CATLG:
      Keep it and catalog it.
    • UNCATLG:
      Keep it and uncatalog it. For default values, consult your JCL reference guide.
  • disp3
    :
    Specifies the disposition of the data set if it is deallocated during abend processing. Specify one of the values that are listed in disp2.
  • unitinformation
    :
    Specifies the unit name that is associated with the unload activity.
  • spaceinformation
    :
    Specifies a how much space should be allocated to a disk data set. This value is required for new data sets and ignored for existing data sets. Specify one of these values:
    • blocks:
      Specifies the size of the disk block to be allocated. The value is generally the same value as the block size of the data set. The allocation routines calculate the physical amount of disk space that is required, based on blocks of the specified size. If specified, both prim and sec are assumed to be in blocks.
    • CYL:
      Specifies the allocation is to be by cylinder. If used, both prim and sec are assumed to specify cylinder.
    • TRK:
      Specifies the allocation is to be by track. If used, both prim and sec are assumed to specify tracks.
  • recfm
    :
    Specifies the record format to be assigned to the data set.
    Permitted values: F, FB, V, VB, and U.
  • lrecl
    :
    Specifies the logical record length that is assigned to the data set.
  • blksize
    :
    Specifies the block size that is assigned to the data set.
  • control statements
    :
    For a detailed control statement syntax overview, see READCMDS Command (CASRV). For line continuation, add a hyphen at the end of the line. For example:
    OPTIONS OPERATION(UNLOAD) - LOGNAME(CA7_LOG_RECORDS) PRODUCT(CA7) OUTDD DDNAME(ALLRECS1) OUTDD DDNAME(ALLRECS2) OUTDD DDNAME(ALLRECS3) METADATA(YES)
  • OPTIONS:
    Controls overall processing of the CALGUNLD utility program.
  • OPERATION=:
    Controls the action of the utility and the disposition of the selected data objects in the log stream.
  • UNLOAD:
    Writes selected data objects to data set referenced by OUTDD and deletes those data objects from the log stream.
  • LOGNAME=:
    Specifies the CA Common Logger managed log stream by LOG name.
  • PRODUCT=:
    Specifies the CA product that was used to register this log stream.
  • OUTDD:
    References a physical sequential data set to which retrieved data objects are written. Any number of OUTDD statements, with corresponding unique DDNAMEs, may be specified. At least one OUTDD statement must be present.
  • DDNAME=
    ddname
    :
    Specifies the keyword DDNAME of a sequential output data set to receive the log records.
  • TYPE=SELECTION|DEFAULT:
    (Optional) Identifies the OUTDD type.
    SELECTION indicates that as log records are passed to OUTDD statements, you want them written to the specified OUTDD statement. Masking is supported.
    DEFAULT is used to capture any records that are not selected by other OUTDD statements using the SELECTION option. When DEFAULT is specified, the only other operand that is allowed is DDNAME. If OPERATION is UNLOAD and if a DEFAULT OUTDD is not specified and a log record is not written to any other OUTDD, CALGUNLD terminates abnormally.
    Default:
    If you do not enter a value, SELECTION is applied.
  • PRODUCT=
    prodmask
    :
    (Optional) Specifies the mask that is used to filter data object written to the OUTDD data set.
  • RELEASE=
    release
    :
    (Optional) Specifies the RELEASE value that is used to filter data object written to the OUTDD data set.
  • INSTANCE=
    instance
    :
    (Optional) INSTANCE value that is used to filter data object written to the OUTDD data set.
  • EXIT=
    exitname
    :
    (Optional) Specifies the exit routine name that receives control before a record is written to the OUTDD data set and before the OUTDD data set is closed.
  • METADATA=YES|NO:
    METADATA=YES causes CALGUNLD to prefix the metadata associated with each record to the data written to the OUTDD statement.
    Default
    : NO
CALOGGER Component Trace
The CA Common Logger Service has component tracing capabilities to capture data about events that occur in the service. Component tracing is accomplished through the CA Common Component Trace Service.
Component Tracing
Component tracing is typically enabled when recreating a problem to provide data to Broadcom Support. Typically, if this action is required, the instructions are supplied by Broadcom Support.
CA Common Logger Service-supported Event IDs
The following table describes the CA Common Logger Service-supported Event IDs:
Event ID
Description
IXGC
CALOGGER IXG* Routine Calls
LAPI
CALOGGER API Calls
LDEV
CALOGGER Device Calls
LGMN
CALOGGER Main Pgm (CALGMAIN)
LQRY
CALOGGER #LGGRQRY Calls
NQDQ
CALOGGER Latch Manager Calls
Examples of Component Tracing
The following topics contain examples of how to use component tracing.
Enable Component Tracing
To enable component tracing for CA Common Logger Service (its Product Code is EF4.):
TRACE CT,ON,COMP=CAMASTER,SUB=(EF4.R150)
When prompted for a reply:
R
nnn
,OPTIONS=(IXGC,LAPI,LDEV,LGMN,LQRY,NQDQ),END
Not all Event IDs must be active. Broadcom Support can indicate which Event IDs to enable to capture the necessary data to debug a problem.
Externalize Component Trace Data
Trace data is externalized through an SVC dump. To externalize the trace data:
TRACE CT,ON,COMP=CAMASTER,SUB=(EF4.R150)
When prompted for a reply,:
R nnn,OPTIONS=(SDUMP),END
Display Component Tracing
To display information about the status of component tracing:
D TRACE,COMP=CAMASTER,SUB=(EF4.R150)
Disable Component Tracing
To disable component tracing:
TRACE CT,OFF,COMP=CAMASTER,SUB=(EF4.R150)
CALOGGER Address Space Shell Operator Commands
Products and components that are hosted in the CALOGGER address space shell support the commands that are described in the following table. The commands support and control the hosted servers and the overall operation of the CALOGGER address space.
Command/Keyword
SAF Authority
Resource Name
Console Authority
ADD[.LOGGER]
CONTROL
jobname
.ADD.LOGGER
SYS
DISPLAY[.LOGGER]
READ
jobname
.DISPLAY.LOGGER
INFO
REMOVE[.LOGGER]
CONTROL
jobname
.REMOVE.LOGGER
SYS