|
|
|
Because of the large number of keywords for the DISPLAY command, the following keywords are grouped alphabetically:
The memory address of the message control block in the CA OPS/MVS main address space. The main address space is called OPSMAIN.
The operating system automation flags for events captured by the CA OPS/MVS subsystem interface exit (SS09). An automation flag is a one-byte hexadecimal value.
The remaining bits are reserved for future use; for now they are always 0.
The ID of the address space that generated this event (ASCBASID). For JES3 sites only: if the event was generated on a different processor or you specified BROWSEMESSAGES(JES3), this value is 0. For details, see How to Control the Way OPSLOG Processes z/OS Messages (JES3 Users Only) in this chapter.
The z/OS automation token for events captured by the subsystem interface exit (SS09) and most commonly used by NetView. You use the AUTO(token) parameter to set this token in the appropriate MPFLSTxx member of the Logical Parmlib Concatenation. You can modify this token in a message rule by modifying the MSG.AUTOTOKN environmental variable. For details, see the IBM documentation.
Same as the value in the AUTOTokn column, except that the value appears in hexadecimal format.
The color the event is displayed in on a color terminal. If the event displays in yellow, this column contains the word yellow displayed in yellow. Possible values are green, yellow, red, blue, white, pink, and turq (for turquoise).
Note: On a monochrome terminal the color name appears, but it does not display in its color.
Synonym for the DSpname keyword. The value in this column depends upon where the event originated. If the event is a message event that originated in the JES3 IATUX31 exit, this value is the name of the JES3 Dynamic Support Program (DSP) that issued the message. Typical JES3 DSP names include CONSERV, PURGE, and SETUP. If the event originated in the generic data set interface or the OMEGAMON interface, this value indicates the report ID associated with the event. If the event originated in the subsystem interface, this value is the name of the console associated with the event.
The number of AOF rules that processed this event.
The date of the event in DD:MMM format; for example, July 11 appears as 11:JUL.
After all applicable rules have executed, the final disposition of the event as determined by the AOF. This column contains no useful information for RULETRACE events. Possible values are:
Default: NOA
Synonym for the CONSNAME keyword. See the CONSNAME keyword.
The amount of elapsed time it took the AOF to process the event. This value is calculated by subtracting the store clock (STCK) value at the end of AOF processing from the beginning STCK value. Typically, if there are no interrupts during processing, the numbers are the same. If an unusually large number appears in this column, the AOF lost control of the CPU during processing of this event due to an input/output interrupt, page fault, or similar occurrence.
The type of AOF event associated with this line in OPSLOG Browse. Event types are:
Note: Event types displayed in lowercase are those that were generated due to the RULETRACE parameter being set to ON.
The identifier of the event (such as IEF250I in the case of a MSG event or DISPLAY in the case of a CMD event).
The EVENTID and MSGID columns display the same data.
The type of system exit in which CA OPS/MVS captured this event (MVS, IMS, OMG, DSN, TRAC, NIP, CICS, CNSV, CA7, API, or NONE). This value indicates the environment in which the AOF ran.
The MCS or IMS message flags associated with the event. The type of flag you see depends on whether the event was captured by the CA OPS/MVS z/OS subsystem interface exit (SS09) or the CA OPS/MVS IMS AOI exit.
Note: For COF events, this column displays the CICS start code.
The ID of the IMS region that generated the event. If the event was not generated by an IMS system on the current processor, the value defaults (usually to NONE).
The type of IMS region in which the address space that generated the event resides. Possible values are:
For JES3 sites only, displays the class of the event. This column contains one of these items: a standard symbolic JES3 message class code, the value NON if the event was not assigned a JES3 message class, or the low-order three hexadecimal digits of the two-byte JES3 class code if one was assigned but CA OPS/MVS failed to decode it. CA OPS/MVS assigns the value of NON to all events z/OS generates when JES3 is down.
Standard JES3 symbolic class codes are:
The JES JOBID of the address space that produced this event.
The name of the job from which the event originated. If the event originated with a server, the value that appears in the JOBNAME column is the started task ID of the server, rather than the actual name of the job.
Started task IDs of servers have been changed from ASIDxxxx to ssidxxxx where ssid is the subsystem ID of the current CA OPS/MVS system, and xxxx is the address space ID of the server (as a hexadecimal value). For example, OPSS0010 is the name of a server for subsystem OPSS in address space x'10'. This permits you to filter events for individual servers or for all servers in OPSLOG Browse.
If multiple copies of CA OPS/MVS are running on one system, only the names of the servers owned by the subsystem you are browsing are changed. Servers owned by other subsystems keep their original names. However, the started task ID changes in all cases.
The subsystem job name/number. For JES3 sites only, this value is the z/OS JOBNAME of the issuer of the event, or NONE. The value is NONE if you specified BROWSEMESSAGES(JES3) and the event originated from IATUX31. For details, see How to Control the Way OPSLOG Processes z/OS Messages (JES3 Users Only) in this chapter.
The event length, not including the length prefix.
The MSF name of the remote copy of CA OPS/MVS to which a rule has sent a message through the OPSSEND function; in other words, the message event destination.
Note: For details about the OPSSEND function, see the Command and Function Reference.
The Multi-System Facility name for the system on which the message event originated. The MSFID column is used when one copy of CA OPS/MVS receives messages from another copy of CA OPS/MVS through an MSF session.
CA OPS/MVS sets a value for MSFID only for unsolicited messages that an AOF rule routes to another machine through the OPSSEND function. For details about the OPSSEND function, see the Command and Function Reference.
A value for MSFID is not set for solicited message events generated in response to a command issued from a remote copy of CA OPS/MVS through the OPSRMT command and returned to the issuing system over the MSF link.
The identifier of the message event (such as IEF250I). A message event identifier is usually just the first token in the message.
CA OPS/MVS contains support for isolating message IDs from unusual messages and providing them to the AOF separately in the MSG variable.
If you find a message event with an ID that CA OPS/MVS is not identifying correctly, call CA customer support.
The sequence number of the event. When data collection begins, the first event OPSLOG Browse collects is 1, the second is 2, and so on. When the capacity of the OPSLOG Browse data area is exhausted, CA OPS/MVS discards the oldest events. Due to this, the first event available from OPSLOG Browse is not necessarily number 1.
If you want to view OPSLOG events without any extra data columns, specify the NONE keyword on your DISPLAY command. If you specify the NONE keyword, it must be the only keyword you specify.
The CA OPS/MVS flag bytes are displayed as four hexadecimal characters. For details, see the AOF Rules User Guide.
The release of the CA OPS/MVS system that captured the event. CA customer support may want to use this value.
The route and descriptor codes of the current event, represented as hexadecimal values. You can use these codes to debug AOF table entries and to analyze console event routing problems.
The extended route and descriptor codes of the event, represented as hexadecimal values.
The name of the last ruleset.rule that processed the event. If no ruleset.rule has processed the event, the value is NONE.NONE.
The special screen character for an event. The primary characters are:
System event; requires action
Problem program event; requires action
Problem program event; no action required
Note: If a problem program tries to counterfeit a system message event by issuing a message with the same message ID as the system message, the attempt fails because z/OS prefixes the message with a plus sign (+). The plus sign permits users and rules to tell the difference.
Any two characters (controlled by the BROWSEIDFORMAT parameter) extracted from the internal system ID field. The internal system field ID contains the name of the system from which the event originated. For JES3 systems, this name is derived from the MPNAME field of the Active Main Processor Control Table. For JES2 systems, the SYSID value is derived from the SMF ID string. For message events where the message has been reissued (for example, JES3 local messages routed by sysplex console services to the global processor), this value is derived from the WQE. This field is primarily intended for use by JES3 sites, but in some cases may also be useful to JES2 sites.
The system name of the system that created the event.
The terminal name associated with an event.
The time when the event appeared (in HH:MM:SS format).
The z/OS-provided time stamp for the event. Since times are given to the second, this value should be the same as the value in the TIME column.
The cross-system WTOID for the event, when the event occurs as a result of the OPSSEND('W') function executing on a remote copy of CA OPS/MVS. For details, see the Command and Function Reference.
The eight-byte value of the MSG.USER variable associated with this event. MSG.USER is an AOF variable that lets rules communicate with one another about a particular message event. Upon entry to the first rule that processes the event, the value of MSG.USER is '00'X. If it is still '00'X upon exit from the last rule, the USER column contains the value NONE. If the value changes, the USER column contains the same value to which MSG.USER was set.
The user ID of the command event issuer for the security product on your system. This is usually the RACF user ID from the ACEE or the CA ACF2 user ID from the ACFASVT. If the event was a command issued from CA Remote Console, this is the user ID of the particular RCS user who issued the command.
Same as the value in the User column, except that in this column the value appears in hexadecimal format.
The WTO sequence number associated with the event.
The four-byte extended console ID associated with the event, expressed as hexadecimals.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |