Messages AMTG
This group includes messages for the
product.
Number | Description |
|---|---|
AMTG11I | LOGGING NOT AVAILABLE, UNABLE TO ALLOCATE LOG Explanation: The LOG data set could not be dynamically allocated. User response: Reenter the command. |
AMTG11I | SYNTAX ERROR Explanation: The LOG command contained a syntax error. User response: Reenter the command. |
AMTG12I | Unable to start logging, BBPARM not allocated Explanation: The product JCL does not contain a BBPARM DD statement pointing to the parameter data set. User response: You may specify the data set name as the second parameter on the LOG command. You may also preallocate the parmlib data set to DDNAME BBPARM either via a DD statement or the TSO ALLOC command as appropriate. |
AMTG13E | Logging requests not allowed at this task level. Explanation: Logging requests are only allowed at the main task level. User response: This is a product error. contact BMC Software Customer Support for assistance. |
AMTG14A | ENTER Y TO TERMINATE LOGGING LIST xx Explanation: Self-explanatory. User response: Enter Y to transfer from one log member to another. |
AMTG15I | ? is an invalid parameter Explanation: The value (?) is not a valid parameter (STOP, FREE, STATUS or a one to two character suffix). The LOGGING service terminates without taking any action. User response: Enter a valid parameter. |
AMTG16I | Unable to locate member $$INLGxx, request ignored. Explanation: Member $$INLGxx could not be found in the parameter data set. User response: Check LOGGING documentation. |
AMTG17I | xxxxxxxx LOGGING NAME NOT UNIQUE, CARD IGNORED Explanation: One of the records in the specified $$INLGxx member does not contain a unique service name. This record is ignored and is not logged. User response: Specify the full service name on the CMD statement. |
AMTG18I | Start rejected. Logging already active. Explanation: Logging can not be started because it is currently active. The LOGGING remains active. User response: Enter LOGGING,STATUS to display the current status. |
AMTG19I | Not all commands accepted; logging request ignored Explanation: Each message listed an invalid service name that was obtained from the $$INLGxx member. The LOGGING service terminates. User response: Correct the $$INLGxx member or use a different member. |
AMTG1AE | xxxxxxxx Service not eligible for logging; request ignored Explanation: The specified logging list contains an entry for a command that cannot be logged. The command is rejected. User response: Correct the the command and retry. |
AMTG1AI | xxxxxxxx SERVICE NOT ELIGIBLE FOR LOGGING; REQUEST IGNORED Explanation: The specified logging list contains an entry for a command that cannot be logged. The command is rejected. User response: Correct the the command and retry. |
AMTG1AW | xxxxxxxx Service not eligible for logging; request ignored Explanation: The specified logging member contains an entry for a service (xxxxxxxx) that cannot be logged (EXECUTE or LOGGING). The command is ignored.' Processing continues. User response: Correct the LOGGING member |
AMTG1BI | AMTG1BI Logging not active, request ignored Explanation: LOGGING was active when the command LOG STOP was entered. The LOGGING service terminates. User response: No action is required. |
AMTG1BI | Open of parmlib data set failed. Logging terminated. Explanation: Parmlib data set could not be opened. The LOGGING service terminates User response: Check to see if an SVC dump was produced. Check the DCB attributes of the parmlib data set. Contact BMC Software Customer Support. |
AMTG1CI | AMTG1CI Logging activity stopped for 12345678 Explanation: Logging was stopped for the specified user in response to a LOG STOP command. LOGGING terminates for the specified user. User response: No action is required. |
AMTG1DE | The following control statement is invalid. Explanation: This message precedes a control statement that contains an error which is listed in message AMTG1EI. The remaining control statements are checked then LOGGING terminates without taking any other action. User response: Correct the control statement(s). |
AMTG1DI | UNABLE TO FREE LOG, LOGGING ACTIVE Explanation: The logging SYSOUT data set cannot be freed for printing unless logging is inactive. User response: Enter LOG STOP and reenter LOG FREE. |
AMTG1EI | control statement Explanation: The control statement is invalid. The remaining control statements are checked then LOGGING terminates without taking any other action. User response: Correct the control statement. |
AMTG1FI | Reading logging parameters from $$INLGxx in dsn Explanation: Informational message indicating the member and data set name providing the logging parameters. User response: No action is required. |
AMTG1GI | Log output will be written to Explanation: This message indicates where output from the Log service will be written. User response: No action is required. |
AMTG1HI | Logging task terminated. Explanation: The logging function stopped. User response: No action is required. |
AMTG1IE | xxxxxxxx is not a valid service name. Request ignored. Explanation: The specified service probably was spelled incorrectly. User response: Check the spelling. |
AMTG1JI | variable Explanation: Messages beginning with AMTG1JI are normal informational messages that are considered self-explanatory. Processing continues User response: No action is required. |
AMTG1KE | Allocation of parmlib data set failed. Logging terminated. Explanation: The Log service has stopped due to an error allocating the parmlib data set. See preceding messages for failure reason. User response: Check for previous messages that explain the error. |
AMTGS1E | Unable to getmain GSDA size of xxxxxxxx Explanation: The GSDA is a common storage work area obtained and used by several services. This message is issued when there is insufficient extended CSA available to satisfy the request. The amount of extended CSA that was requested is displayed in the message. The requesting service is terminated with a User 78 abend. User response: Consider increasing the amount of extended CSA. |
AMTGT3W | SYSPROG SERVICES CANNOT USE COMMON MEMORY OBJECTS Explanation: The product always issues this message with AMTGT4W and AMTGT5W: AMTGT3W SYSPROG SERVICES CANNOT USE COMMON MEMORY OBJECTS These messages indicate that, for system integrity reasons, SYSPROG Services cannot create user-key common memory objects. Consequently, SYSPROG Services will use conventional common storage, instead. The product continues to run normally, but with an increased use of conventional common storage. User response: Consider running SYSPROG Services in a system key to allow using common memory objects. Doing so can reduce the use of conventional common storage and improve system integrity. Also, consider either removing ALLOWUSERKEYCSA(YES) from DIAGxx or changing it to ALLOWUSERKEYCSA(NO). |
AMTGT4W | because it is executing in user key x See the explanation for AMTGT3W. |
AMTGT5W | Conventional common storage will be used See the explanation for AMTGT3W. |