QUERY LOGMSG

Read syntax diagramSkip visual syntax diagram Query LOGmsg 1ACCountaccountidACIgroupgroupnameSystemUseriduserid*2ContentsORIGinDBCSSBCS
Notes:
  • 1 Options are valid only for class B users.
  • 2 If QUERY LOGMSG is executed with the AT command, the * operand is not allowed.

Authorization

Privilege Class: A, B, C, D, E, F, G

Purpose

Use QUERY LOGMSG to display the system log messages. The log messages can reside in either a CMS file or the checkpoint area.

If the FEATURES ENABLE LOGMSG_FROM_FILE statement is specified in the system configuration file, CP reads the CMS files on the CP-accessed minidisks to determine which log message files to display, and the QUERY LOGMSG command options are valid for a class B user. For more information on the FEATURES statement, see z/VM: CP Planning and Administration.

If the FEATURES ENABLE LOGMSG_FROM_FILE statement is not specified in the system configuration file, CP displays the log message saved by the SET LOGMSG command.

Operands

ACCount accountid
tells CP to display either the contents or origin information of the file that only users whose account ID (set in the user's directory entry) matches accountid would see. If you are using a non-DBCS terminal and have not specified the DBCS option, CP searches for a file called accountid LOGMSACC on the lowest accessed CP disk. If you are using a DBCS terminal or have specified the DBCS option, CP searches for a file called accountid LOGDBACC on the lowest accessed CP disk. If no such file exists, CP searches for a file called accountid LOGMSACC.
ACIgroup groupname
tells CP to display either the contents or origin information of the file that only users who are in the ACI group identified by groupname would see. If you are using a non-DBCS terminal and have not specified the DBCS option, CP searches for a file called groupname LOGMSACI on the lowest accessed CP disk. If you are using a DBCS terminal or have specified the DBCS option, CP searches for a file called groupname LOGDBACI on the lowest accessed CP disk. If no such file exists, CP searches for a file called groupname LOGMSACI.
System
tells CP to display either the contents or origin information of the file that all users of the system would see. If you are using a non-DBCS terminal and have not specified the DBCS option, CP searches for a file called SYSTEM LOGMSG on the lowest accessed CP disk. If you are using a DBCS terminal or have specified the DBCS option, CP searches for a file called SYSTEM LOGDBCS on the lowest accessed CP disk. If no such file exists, CP searches for a file called SYSTEM LOGMSG.
Userid userid
tells CP to display either the contents or origin information of the file that only the specified userid would see. If you are using a non-DBCS terminal or have not specified the DBCS option, CP searches for a file called userid LOGMSUSR on the lowest accessed CP disk. If you are using a DBCS terminal or have specified the DBCS option, CP searches for a file called userid LOGDBUSR on the lowest accessed CP disk. If no such file exists, CP searches for a file called userid LOGMSUSR.
Userid *
tells CP to display either the contents or origin information of the file that only your user ID would see. If you are using a non-DBCS terminal or have not specified the DBCS option, CP searches for a file called userid LOGMSUSR on the lowest accessed CP disk. If you are using a DBCS terminal or have specified the DBCS option, CP searches for a file called userid LOGDBUSR on the lowest accessed CP disk. If no such file exists, CP searches for a file called userid LOGMSUSR. In either case, userid is the user ID of the command issuer.
Contents
tells CP you wish to see the contents of a file. This is the default.
ORIGin
tells CP you wish to see on which CP-accessed minidisk the file resides instead of seeing the contents of the selected file.
DBCS
tells CP you wish to see origin information or content for the file that would be displayed to users on DBCS-capable terminals. If neither DBCS nor SBCS are specified, CP assumes you wish to see origin information or content for the file that would be displayed to users on terminals similar to your own.
SBCS
tells CP you wish to see origin information or content for the file that would be displayed to users on SBCS-capable terminals. If neither DBCS nor SBCS are specified, CP assumes you wish to see origin information or content for the file that would be displayed to users on terminals similar to your own.

Usage Notes

  1. If the file-based LOGMSG support is not enabled through the FEATURES statement in the system configuration file, QUERY LOGMSG cannot be entered with additional operands.
  2. If you enable the file-based LOGMSG support but you do not also enable the LOGMSG support for account IDs, ACI groups, and user IDs, CP searches only for a file called SYSTEM LOGMSG (or SYSTEM LOGDBCS if you are on a DBCS terminal).
  3. If you enter the QUERY LOGMSG command with no additional operands, you have enabled the file-based LOGMSG support, and you have also enabled LOGMSG support based on account IDs, ACI groups, or user IDs, CP displays the contents of the appropriate files in the following order:
    • System log message
    • Account log message
    • ACI group log message
    • User log message.
    You will be unable to determine where the contents of one file ends and the contents of the next file begins by looking at the response to the QUERY LOGMSG command.
  4. If you are a class G user and you enter the QUERY LOGMSG command, you see a log message containing information seen by everyone, information seen only by other users that have your account ID, information seen only by other users that are in the same ACI group as you, and information seen only by you.
  5. When you log on, CP processes a special QUERY LOGMSG on your behalf. Only records beginning with an asterisk (*) are displayed in response to this command. If you enter a QUERY LOGMSG, all records in the log message are displayed.
  6. To change the contents of the log message, you must first determine whether you have enabled the file-based LOGMSG support. If you have enabled the file-based LOGMSG support, you must edit the files containing the log messages and enter the CPACCESS command to have CP access the changed files. If you have not enabled the file-based LOGMSG support, you must use the SET LOGMSG command to change the contents of individual lines in the log message.

Responses

If there is no log message data available, you get this response: 
There is no logmsg data
Otherwise, the contents of the log message, preceded by the LOGMSG header, are displayed on your terminal.

If old-style log message support is in effect, class B users see each line of log message data preceded by a line number. These numbers allow class B users to edit the log message using the class B SET LOGMSG command.

When you specify ORIGIN on the command, you get this type of response: 
LOGMSG file SYSTEM LOGMSG located on CP accessed disk A (MAINT's 300).
If the requested file does not exist, you see this: 
LOGMSG file MAINT LOGMSUSR not located on any CP-accessed disk.

Messages

  • HCP002E Invalid operand - operand
  • HCP003E Invalid option - command contains extra option(s) starting with operand
  • HCP007E Invalid userid - userid
  • HCP026E Operand missing or invalid
  • HCP041E LOGMSG nn does not exist.
  • HCP1506E The last line (50) in the log message is already in use.
  • HCP6704E Missing token at end of line
  • HCP6706E Invalid {group name|account ID} - {groupname|accountid}
  • HCP6734E Support for file-based LOGMSG is not enabled.
  • HCP6771E LOGMSG support based on {Account ID|ACI group|Userid} is not enabled.