Messages HSAM1000I to HSAM5411I
HSAM1000I AUTOMATION MANAGER SUBTASKS ARE BEING STARTED.
Explanation
The basic initialization step of the SA z/OS automation manager has successfully completed. All subtasks are being attached and the main task will wait observing the subtasks.
System action
The SA z/OS automation manager continues with the initialization.
Operator response
None.
System programmer response
None.
HSAM1001I THE KEY keyword CANNOT BE RETRIEVED FROM PKVT, CONTINUE WITH DEFAULT VALUE: default value.
Explanation
A keyword cannot be resolved. The key value specified in the parmlib member will be ignored.
- The variable keyword shows the start parameter that can be modified in the parmlib member.
- The variable default value shows the default value specified for the keyword. If the default value is blank, this field may be blank.
System action
The SA z/OS automation manager continues with the initialization.
Operator response
None.
System programmer response
Contact your IBM® Support Center.
HSAM1002I AUTOMATION MANAGER INITIALIZATION DETECTED THAT THE SUBSYSTEM subsystem IS MISSING OR CONFLICT DETECTED WITH PARMLIB PARAMETERS COMM/MQM.
Explanation
The automation manager needs the specified system component for initialization.
- The variable component shows the required system component, for example, the OMVS kernel or the WebSphere MQ Manager.
System action
The SA z/OS automation manager terminates.
Operator response
Inform your system programmer.
System programmer response
Start the required system component. Examine the automation manager PARMLIB member for correct specification of the COMM
and MQM parameters. If COMM=XCF, the MQM parameter must not be specified. If
COMM=MQ, a valid WebSphere MQ subsystem
name must be specified for the MQM parameter.
HSAM1003I ARM function WAS SUCCESSFUL FOR ELEMENT=element TYPE=type restart.
Explanation
An ARM function (either register or deregister) could be successfully completed.
- The variable function shows the ARM function. It can be either register or deregister.
- The variable element shows the ARM element, representing the SA z/OS automation manager.
- The variable type shows the type of the ARM element SA z/OS automation manager.
- The variable restart shows whether the automation was restarted by ARM or not (RESTART=YES or RESTART=NO.)
System action
The SA z/OS automation manager continues initializing being ARM enabled.
Operator response
None.
System programmer response
None.
HSAM1004I ARM function FAILED FOR ELEMENT=element TYPE=type, IXCARM RET=RC RSN=RSN restart.
Explanation
An ARM function (either register or deregister) could not be completed successfully.
- The variable function shows the ARM function. It can be either register or deregister.
- The variable element shows the ARM element, representing the SA z/OS automation manager.
- The variable type shows the type of the ARM element "SA z/OS automation manager" and optionally the restart type which informs you whether the automation was restarted by ARM or not (RESTART=YES or RESTART=NO or RESTART=ERR).
- The variable RC shows the return code of the ARM function.
- The variable RSN shows the reason code of the ARM function. If the Automation Manager retries ARM registration due to parameter ARMWAIT=nnn in parmlib member HSAPRMxx then the variable RSN has a suffix ",RETRY...". This informs you that the Automation Manager is waiting for ARM to be up.
System action
The SA z/OS automation manager continues initializing without being ARM enabled. If RESTART=ERR then the SA z/OS automation manager was restarted on a different MVS system. In this case, the SA z/OS automation manager terminates.
Operator response
None.
System programmer response
Verify if ARM was correctly customized for the SA z/OS automation manager. If necessary, contact your IBM Support Center.
HSAM1005I COMMUNICATION IS XCF ONLY. THE TAKEOVER FILE WILL BE USED FOR HOT START AND RECOVERY PURPOSES.
Explanation
The automation manager does not use MQ Series, neither for the communication with the automation agents nor for recording the current status and settings of the resources. Instead XCF is used for the communication with the automation agents.
The automation manager records all changes made to the resources in the takeover file identified by DD-name HSATKOVR. In case of an abend or any normal takeover (hot start), the automation manager reads the takeover file to restore the most current status of the resources.
Note that any request that has not yet been processed by the automation manager will be lost and cannot be recovered in case of an abend or any regular takeover.
System action
None.
Operator response
None.
System programmer response
None.
HSAM1006E PARAMETER option CANNOT BE RETRIEVED FROM PARMLIB.
Explanation
The named parameter is mandatory but not specified in the HSAPRMxx parmlib member that is used at the startup time of the automation manager.
- The variable option is the name of the parameter that is missing.
System action
The SA z/OS automation manager terminates.
Operator response
None.
System programmer response
Add the parameter in the HSAPRMxx parmlib member that is used at the startup time of the automation manager.
HSAM1010I AUTOMATION MANAGER TERMINATION COMPLETE, REASON CODE = reason code
Explanation
- 0
- Successful completion
- 1
- Implicit normal termination due to directed takeover (changed operation mode from SAM to PAM)
- 4
- Stop Immed
- 8
- Stop Force
- 20
- Initialization failed because MTIB could not be created
- 24
- Initialization failed because MTIB Vector could not be created
- 28
- Initialization failed because a task could not be created
- 32
- Initialization failed because a task could not be attached
- 33
- Initialization stopped but no takeover is performed
- 34
- Either the initial storage check failed, or a GETMAIN service abended after initialization due to a storage shortage. The automation manager needs a minimum of 40 MB free storage.
- 35
- ARM (De)Reg failed
- 36
- z/OS UNIX System Services has canceled the job
- 39
- An I/O error occurred for the takeover file
- 40
- Implicit normal or forced termination due to error detected by observer
- 44
- The subsystem is missing
- 45
- z/OS does not meet the prerequisites
- 48, 52
- C++ task failed. This is probably an exception
- 56
- LE task abended
- 60
- Task abended
- 64
- LE user abend
- 72
- Bad return code from subtask shell function
- 76
- Event handler detected an error
- 80
- The job was canceled
Note that for all return codes < 40 no ARM restart is performed. It will be suppressed even if
ARM is enabled, except for /F jobname,STOP,..,RESTART.
System action
The SA z/OS automation manager terminates.
Operator response
None.
System programmer response
Analyze the reason code and, if issued, the HSAM1050E error message.
HSAM1011I CURRENT Z/OS SYSTEM DOES NOT MEET AUTOMATION MANAGER PREREQUISITES: xxxx
Explanation
The automation manager requires a z/OS prerequisite that is not met by the current z/OS system. The following prerequisites may be detected:
- z/OS < 1.9
- The release of z/OS is earlier than V1.9.
System action
The SA z/OS automation manager terminates.
Operator response
None.
System programmer response
Run the automation manager on a z/OS system that meets the specified prerequisites.
HSAM1050E AUTOMATION MANAGER ERROR DIAGNOSIS: SYSTEM=system TASK=task name ERRTYPE=error type ERRCODE=error code SERVICE=service RC=return code RSN=reason code DIAG=diagnostic
Explanation
This is a generic error message that provides a detailed problem description of an error that was detected during automation manager processing.
- The variable system shows the name of the MVS system where the error was detected.
- The variable task name shows the name of the automation manager task that causes the error.
- The variable error type shows the type of the error. The following values can
occur:
- 4
- Input checking failed.
- 8
- Initialization error.
- 12
- Termination error.
- 16
- An internal sysplex communication pipe service provided by an SA z/OS system failed.
- 20
- RPC Command Handler failed.
- 24
- A system service named by SERVICE, such as the MVS request IXCJOIN, failed.
- 32
- Storage problem.
- 36
- Internal error. Note: An internal error 36, combined with RC=00000EC6 and RSN=0000FF09 may indicate automation manager termination due to OMVS shutdown.
- 40
- Environment error.
- The variable error code shows a unique number to determine the location in
the code where the error was detected.
See AOF350E for diagnostic information about combinations of error type and error code.
- The variable service shows the name of the service that caused the error.
- The variable return code shows the return code of the failing service (hex number). This token is specified together with service.
- The variable reason code shows the reason code of the failing service (hex number). This token is specified together with service.
- The variable diagnostic shows diagnostic information in a string of tokens. The first token specifies the name of the failing module. All remaining tokens vary depending on the error code. Data provided by diagnostic is intended for IBM service
- personnel.
For further information about the combinations of error types and error codes and their meaning, refer to AOF350E.
System action
None.
Operator response
None.
System programmer response
Look into the table for combinations of error type/codes for a detailed explanation of the error. Examine the return code and reason code of the failing service if available. If necessary, contact your IBM Support Center.
HSAM1051E SYSPLEX COMMUNICATION MANAGER INITIALIZATION FAILED.
Explanation
An error was detected during initialization of the sysplex communication manager task in the SA z/OS automation manager.
System action
The SA z/OS automation manager terminates.
Operator response
None.
System programmer response
Look for additional HSAM1050E messages that are issued with this message.
HSAM1052I SYSPLEX COMMUNICATION MANAGER INITIALIZATION COMPLETE.
Explanation
The sysplex communication manager task of the SA z/OS automation manager could be successfully initialized and is ready to receive.
System action
The SA z/OS automation manager continues with the initialization.
Operator response
None.
System programmer response
None.
HSAM1059I DIAGNOSTIC INFO: MOD=module INCIDENT=incident diagnostic-text
Explanation
The purpose of this message is to provide diagnostic information to IBM service staff.
- The variable module shows name of the module that detected the incident.
- The variable incident shows a unique ID for an internally detected incident.
- The variable diagnostic-text shows useful text in free format. The text
depends on the incident that occurred. For example, for
INCIDENT=100, this is the duplicate handle + seq-number.
System action
Processing continues.
Operator response
None.
System programmer response
None.
HSAM1301I SA z/OS AUTOMATION MANAGER WAITING FOR INITIALIZATION DELAY COMPLETION.
Explanation
An automation manager initialization delay of greater than 30 seconds was specified. The specified delay allows another automation manager to assume priority control of the automation sysplex if started within the delay period.
System action
The SA z/OS automation manager suspends initialization until the specified delay expires or is canceled through an operator command. This message is deleted when the specified delay is no longer in effect.
Operator response
The delay may be canceled by routing an MVS Modify(F) <jobname>,GO command to the issuing system image.
System programmer response
None.
HSAM1302A SPECIFY SA z/OS AUTOMATION CONFIGURATION DATA SET NAME.
Explanation
The SA z/OS automation manager has been started with PROMPT=YES in effect. If requested, this message will appear on the first SA z/OS automation manager instance to assume control of the automation sysplex following a sysplexwide IPL or similar automation shutdown.
System action
The SA z/OS automation manager waits for a response to this request.
Operator response
A null or asterisk (*) response may be used to indicate that the default data set as determined by the start type is to be used. For a warm start, this default is the data set that was in use when the previous primary automation manager instance terminated. For a cold start, the default is the data set or generation data group (GDG) member as specified for the installation through the selected parmlib member.
The response may also be a fully qualified data set or GDG member name. If the default configuration data set is a GDG member, a different member of the same GDG may be specified using an asterisk followed by the relative GDG number in parentheses, for example, *(0) or *(-1).
System programmer response
None.
HSAM1303I SA z/OS AUTOMATION MANAGER IS WAITING FOR MQSERIES CONNECTION
Explanation
The SA z/OS automation manager is checking whether MQSeries® is ready.
System action
If MQSeries is not ready the SA z/OS automation manager retries until the TAKEOVERTIMEOUT defined in the parmlib is expired. If it is expired the SA z/OS automation manager switches from hot to warm start.
Operator response
None.
System programmer response
None.
HSAM1304A SPECIFY SA z/OS AUTOMATION CONFIGURATION DATA SET NAME.
Explanation
The SA z/OS automation manager was unable to determine or otherwise process the configuration data set as specified through the HSAM1302A response, or defaulted from prior use. Additional messages will indicate any errors encountered while attempting to process the specified or default data set.
System action
The SA z/OS automation manager waits for a response to this request.
Operator response
The response must be the fully qualified MVS data set or GDG member name containing the SA z/OS configuration data. If the default configuration data set is a GDG member, a different member of the same GDG may be specified using an asterisk followed by the relative GDG number in parentheses, for example, *(0) or *(-1). The automation manager may also be stopped if no valid configuration data is available.
System programmer response
None.
HSAM1305I UNABLE TO PROCESS SA z/OS AUTOMATION CONFIGURATION DATA SET dataset
Explanation
The SA z/OS automation manager was unable to dynamically allocate the named configuration data set. The named data set name was successfully allocated, but cannot be used by the issuing automation manager instance. Additional messages will indicate any errors encountered while attempting to process the specified or default data set.
- The variable dataset shows the name of the configuration data set that could not be allocated dynamically.
System action
The SA z/OS automation manager instance prompts for a new configuration data set name via message HSAM1304A.
Operator response
Check that the data set has not been incorrectly modified prior to starting the affected automation manager instance. Also check whether all copy operations from the configuration dialog output completed successfully. Respond to the HSAM1304A prompt with a new or backup data set name as described in the installation procedures.
System programmer response
None.
HSAM1306I UNABLE TO ALLOCATE SA z/OS AUTOMATION CONFIGURATION DATA SET dataset
Explanation
The SA z/OS automation manager was unable to dynamically allocate the named configuration data set. The data set name could not be allocated or is not a partitioned data set. Additional dynamic allocation messages will indicate any errors encountered while attempting to allocate the data set.
- The variable dataset shows the name of the configuration data set that could not be allocated dynamically.
System action
The SA z/OS automation manager instance prompts for a new configuration data set name via message HSAM1304A.
Operator response
Check that the data set name is correct and that it is a correctly catalogued partitioned data set. Respond to the HSAM1304A prompt with a new or backup data set name described in the installation procedures.
System programmer response
None.
HSAM1307I SA z/OS SECONDARY AUTOMATION MANAGER INITIALIZATION COMPLETE.
Explanation
The SA z/OS automation manager instance has completed initialization as a secondary manager, and is ready to assume automation sysplex control with minimum delay in case the primary manager terminates.
System action
The SA z/OS automation manager instance monitors for changes in the configuration status, and attempts to assume control of the automation sysplex in case the primary automation manager terminates.
Operator response
None.
System programmer response
None.
HSAM1308I SA z/OS PRIMARY AUTOMATION MANAGER INITIALIZATION COMPLETE, TYPE=type
Explanation
The SA z/OS automation manager instance has completed initialization as the primary automation manager, and has assumed control of the automation sysplex.
- The variable type shows the start type. It can be COLD, WARM, or HOT.
System action
The SA z/OS automation manager instance monitors for changes in the configuration status, and is ready to service requests from all automation agents defined to the automation sysplex.
Operator response
None.
System programmer response
None.
HSAM1309I SA z/OS PRIMARY AUTOMATION MANAGER HOT TAKEOVER COMPLETE.
Explanation
Issuing an INGAMS REFRESH command while an Agent is SUSPENDED will interfere with the still ongoing load process and will result in a delay for the processing of the INGAMS REFRESH command. It is recommended that you wait until all agents are in the READY status before issuing the INGAMS REFRESH command.
System action
The SA z/OS automation manager instance monitors for changes in the configuration status, and is ready to service requests from all automation agents defined to the automation sysplex.
Operator response
None.
System programmer response
None.
HSAM1310I RC=rc REAS=reason OPCODE=@5 (@3.@4) @6.
Explanation
This is an internal message for diagnostic purposes only.
Ignore messages with RC=2.
System action
None.
Operator response
None.
System programmer response
Contact your IBM Support Center.
HSAM1311I @1
Explanation
This is an internal message for diagnostic purposes only.
System action
None.
Operator response
None.
System programmer response
None.
HSAM1314I TAKEOVER WILL BE DELAYED FOR timeout SECONDS.
Explanation
Takeover will be delayed for a number of seconds if it is done from the VSAM takeover file.
- The variable timeout is taken from the TAKEOVERTIMEOUT parameter of the HSAPRMxx parmlib member.
System action
Processing continues. Any stop command is accepted but does not cause termination until the time that is specified in TAKEOVERTIMEOUT has expired.
Operator response
None.
System programmer response
None.
Classes
None.
HSAM1315I SUCCESSFUL ALLOCATION OF TAKEOVER FILE dataset_name.
Explanation
The automation manager issues this message when the takeover file has been allocated successfully.
- The variable dataset_name is the name of the takeover file as specified in the HSAPRMxx parmlib member.
System action
The SA z/OS automation manager continues with initialization.
Operator response
None.
System programmer response
None.
HSAM1316I ALLOCATION OF TAKEOVER FILE dataset_name FAILED WITH RC=code: DIAGNOSTIC INFO RETCODE=retcode REASON=reason.
Explanation
The automation manager tried to allocate the specified takeover file but this failed.
- The variable dataset_name is the name of the takeover file as specified in the HSAPRMxx parmlib member.
- The variable code explains why the allocation failed. It can have the
following values:
- 98
- No more memory
- 99
- Invalid input parameter
- 10nn
- Allocation failed
- 20nn
- Deallocation failed
- 8
- Invalid data set name, member name, or DD-name.
- 12
- Allocation error. retcode and reason are the return code and reason code from the SVC 99 (DynAlloc).
- The variable retcode gives more details about why the allocation failed.
- The variable reason is the reason code.
System action
The automation manager continues and issues message HSAM1317A, asking the operator how to continue.
Operator response
None.
System programmer response
Analyze why the allocation failed. Look for additional messages (HSAL1105E in case of an I/O error) that are issued with this message.
HSAM1317A REPLY "HOT" TO RETRY HOT-START OR "WARM" TO CONTINUE WITH WARM-START OR "CANCEL".
Explanation
During the initialization of the automation manager performing a hot-start, an error occurred while accessing the takeover file. Either the allocation failed or a VSAM read/write error occurred or the takeover file was disabled by the previous PAM.
System action
The automation manager waits for an operator response.
Operator response
- HOT
- To retry hot-start processing by allocating the takeover file again.
- WARM
- To continue with a warm start.
- CANCEL
- Results in HSAM1390E with the option to stop the automation manager.
System programmer response
None.
HSAM1318D Reply "NOSUSPEND" or "FORCESUSPEND" to continue or "CANCEL".
Explanation
During the initialization of the automation manager performing a COLD or WARM start, the processing of the suspend file failed due to an allocation failure, a read error or syntax error(s).- The NOSUSPEND option continues the automation manager's initialization without processing the suspend file.
- The FORCESUSPEND option continues processing the suspend file and ignores possible errors.
- The CANCEL option stops the automation manager.
System action
The automation manager waits for an operator response.Operator response
Specify one of the valid options.System programmer response
None.HSAM1319I INPUT DATA NOT ACCEPTED
Explanation
A WTOR was issued and asked the operator to enter input data. However, the input data was incorrect.System action
The WTOR is reissued to ask for valid input data.Operator response
Enter the correct input data. See message text of the corresponding WTOR.System programmer response
None.HSAM1320E SA z/OS AUTOMATION MANAGER request REQUEST TIMED OUT.
Explanation
The named internal automation manager request did not complete within the time limit associated with the request.
- The variable request shows the name of the request that timed out.
This may be due to temporary system performance factors, delays caused by an unusual amount of automation activity, or problems processing the named request.
System action
The SA z/OS automation manager instance continues monitoring for commands and configuration changes, and resumes normal operation when the named request completes. The message will also be deleted when the request has completed.
Operator response
If this message appears often or remains outstanding for an extended period, advise your system programmer of the condition.
System programmer response
Investigate the following request specific possibilities:
- AMS_READ_CONFIGURATION
This request is issued during Primary automation manager startup, automation manager takeover, and when a configuration refresh is requested. If the message appears during a hot start or takeover operation, the delay is probably MQSeries related. If it appears during a Warm or Cold start, or configuration refresh operation, the delay is probably I/O related.
Another reason might be that the automation manager does not run as super user for UNIX System Services or one of your file system management address spaces does not run with SUB=MSTR. See also message HSAL1083I for more information.
- AMS_APPLY_CONFIGURATION
While the timeout value for most automation manager requests is determined by IBM, the AMS_APPLY_CONFIGURATION timeout value may be specified through the HSAPRMxx parameter member. The time necessary to complete this function depends on the number of resources defined, and the temporary appearance of the HSAM1320E message may indicate that the specified or default timeout value is too low.
HSAM1321I SA z/OS AUTOMATION AGENT request REQUEST TIMED OUT.
Explanation
An automation agent request did not complete within the time limit. This may be due to temporary system performance factors, delays caused by an unusual amount of automation activity, or problems processing the named request.
- The variable request shows the name of the request that timed out.
For a configuration refresh it is required that check ACF is complete on all agents. Note that a configuration refresh operation is considered complete when the automation manager configuration has been updated, and does not require that all automation agents have completed their corresponding configuration update activity.
System action
The SA z/OS automation manager instance continues monitoring for commands and configuration changes, and resumes normal operation when the named request completes. The message will be deleted when a response was received from all affected agents.
Operator response
Verify that all active automation agents appear to be working correctly and are communicating with the automation manager.
If this message appears often or remains outstanding for an extended period, advise your system programmer of the condition.
System programmer response
None.
HSAM1323I UNABLE TO OBTAIN PREVIOUS CONFIGURATION INFORMATION, RC=rc, Reason=reason.
Explanation
The SA z/OS automation manager was unable to read the data set defined by the HSACFGIN DD statement.
- The variable rc shows the value of the return code.
- The variable reason shows the value of the reason code.
System action
The SA z/OS automation manager instance terminates.
Operator response
Check that the data set defined by the HSACFGIN DD statement of the automation manager start procedure is available and correctly initialized. Restart the automation manager using an alternate data set if available, or contact your systems programmer.
System programmer response
All instances of the automation manager within the automation sysplex must point to the same CFGINFO data set. A new data set can be initialized by starting the automation manager with TYPE=COLD.
HSAM1324E UNABLE TO UPDATE CONFIGURATION INFORMATION, RC=rc, REASON=reason
Explanation
The SA z/OS automation manager could not update the data set defined by the HSACFGIN DD statement.
- The variable rc shows the value of the return code.
- The variable reason shows the value of the reason code.
System action
If this message appears during initial automation manager startup, the instance continues to run normally. However, a subsequent warm may not be possible. If the error occurs during a configuration refresh operation, the configuration refresh will be aborted.
Operator response
Check that the data set defined by the HSACFGIN DD statement of the automation manager start procedure is available and correctly allocated. Also check that the automation manager has the necessary authorization to update it. When the problem is resolved, perform a configuration refresh using the correct data set name.
System programmer response
All instances of the automation manager within the automation sysplex must point to the same CFGINFO data set. Also, all automation manager instances must have the correct SAF authority to allow it to be updated. If the instance was started with TYPE=COLD, this may be the initial access to the data set. Otherwise, the data set is opened and read during automation manager initialization.
HSAM1330I request REQUEST COMPLETED SUCCESSFULLY ON agent.
Explanation
An automation manager request has successfully completed on an automation agent.
- The variable request shows the request that was completed.
- The variable agent shows the name of the automation agent.
System action
The SA z/OS automation manager instance continues normal processing relative to the identified automation agent.
Operator response
None.
System programmer response
None.
HSAM1331I request REQUEST FOR agent FAILED
Explanation
An automation manager request failed on an automation agent.
- The variable request shows the request that failed.
- The variable agent shows the name of the automation agent.
System action
The automation manager action depends on the request that failed and on the reason why the request was issued. In general however, the actions are as follows:
- Load_ACF Request
The affected agent is unable to initialize or perform automation until the cause of the failure is identified and resolved. The most common cause of this failure is a mismatch between the ACF available to the agent and the current automation manager configuration. Additional automation agent messages may provide more detailed information about the reason for the failure.
- Check_ACF request
This request is normally issued during a configuration refresh operation to verify that the new configuration is available to all automation agents. The configuration refresh operation is terminated as a result of this condition.
- Refresh_ACF
This request is normally issued at the end of a configuration refresh operation to activate the revised ACF. The affected agent should continue to operate in a compatible manner with the new configuration using the previously active ACF data. Thus, newly added resources will not be automated and existing resources will be automated using the previously defined automation policy.
Operator response
Contact your system programmer. When the problem has been resolved, reissue a configuration refresh command to retry the failed request.
System programmer response
The most common cause of Load_ACF failure is that the ACF available to the automation agent is incompatible with the current manager configuration. Similarly, a Check_ACF failure often indicates an incompatibility between the available ACF and the new automation manager configuration. Other possible causes include corruption of the ACF content and various other problems verifying its content. The reporting automation agent should provide additional information about the reason for the failure.
The failure of a Refresh_ACF request indicates problems were encountered while activating the changes contained in the new configuration. Any resources that were deleted or added by the new configuration will not be automated, and existing resources will be automated using the previous agent policy.
HSAM1332I INVALID response RESPONSE FROM agent, REASON=reason.
Explanation
An invalid response for a request was received from an automation agent.
- The variable response shows the invalid response that the automation agent issued.
- The variable agent shows the name of the automation agent that issued the response.
- The variable reason shows the value of the reason code that the automation agent issued.
System action
If the request is Check_ACF, the associated configuration refresh operation will be terminated. Otherwise, the automation manager operation continues as if the return code had been zero.
Operator response
Report the message to your system programmer. Check whether the identified agent operates correctly. Also check whether any error messages are issued that indicate problems when processing the named request.
System programmer response
This message indicates a software problem. Report the problem to your IBM Support Center.
HSAM1333I request REQUEST PROCESSED ON agent.
Explanation
The automation manager has completed processing of a request.
- The variable request shows the name of the request.
- The variable agent shows the name of the automation agent where the request was processed.
Normally, the automation manager then goes back to ready state. However, this message does not confirm that the request was processed successfully. It may also have failed. In case of a failure, an additional message may be issued, for example, if a refresh request fails, message HSAM1337I is issued.
System action
The SA z/OS automation manager instance continues processing normally. Additional messages, for example message HSAM1330I, may be issued due to events that are received later on.
Operator response
None.
System programmer response
None.
HSAM1336I UNABLE TO PROCESS THE SUSPEND FILE dataset_name.
Explanation
A configuration refresh could not finish successfully. The automation manager was unable to process the suspend file for one of the following reasons:- The file was not allocated successfully.
- The file could not be read.
- Access rights are not defined correctly.
- A syntax error occurred when checking the file content.
Additional messages will indicate any errors encountered while attempting to process the specified suspend file.
System action
The previous configuration remains active.Operator response
Verify that the suspend file exists and the access rights are correctly defined. Look for additional messages that may describe the reasons for the error.System programmer response
None.HSAM1337I CONFIGURATION REFRESH REQUEST TERMINATED.
Explanation
A configuration refresh request has been terminated due to errors or automation agent incompatibilities. No changes to the automation manager configuration have been implemented and no automation agent updates have been scheduled as a result of the request.
System action
Automation continues using the configuration in effect when the request was issued.
Operator response
Check for other messages indicating the reason for the termination of the request. Determine the cause of the error and correct your data. Then reissue the request.
System programmer response
None.
HSAM1338I CONFIGURATION REFRESH REQUEST COMPLETED WITH AGENT UPDATE ERROR INDICATIONS.
Explanation
A configuration refresh request has completed successfully on the automation manager. However, one or more automation agents have reported problems when implementing the ACF changes. Message HSAM1331I contains more information about the affected agent(s), and the individual agents should have issued messages indicating the problem details.
System action
Automation continues using the new automation manager configuration. The affected agent(s) should continue to operate in a compatible manner with the new configuration using the previously active ACF data. Thus, newly added resources will not be automated. Existing resources will be automated using the previously defined automation policy.
Operator response
Contact your system programmer. When the cause has been determined, issue a configuration refresh command to retry the failed request.
System programmer response
Check for automation agent error messages indicating the cause of the ACF refresh failure and correct your data accordingly.
The failure of a Refresh_ACF request indicates problems were encountered while activating the changes contained in the new configuration. Any resources that were deleted or added by the new configuration will not be automated. Existing resources will be automated using the previous agent policy.
HSAM1339I CONFIGURATION REFRESH REQUEST COMPLETED SUCCESSFULLY.
Explanation
This message is issued when a configuration refresh request has been completed successfully. It indicates that the primary automation manager and all SA z/OS automation agents within the automation sysplex have processed the request and have indicated normal completion of the update process.
System action
Automation continues using the requested configuration.
Operator response
None.
HSAM1360I UNABLE TO RETRIEVE RECOVERY INFORMATION - WARM START RECOVERY IN PROGRESS.
Explanation
A takeover or startup with TYPE=HOT cannot complete because the recovery information needed to do so is either unavailable or has been invalidated.
System action
The automation manager performs a warm start to reach an operational state. Automation continues after the warm start operation completes. This operation may take some time to complete because each automation agent must reconnect with the automation manager and present status for all resources under its control.
Operator response
Any automation manager requests that were incomplete when the previously active PAM terminated may need to be resubmitted.
System programmer response
None.
HSAM1361I UNABLE TO PROCESS RECOVERY INFORMATION - ABNORMAL TERMINATION IN PROGRESS
Explanation
A takeover, ARM restart, or restart with TYPE=HOT cannot complete because the recovery information needed to do so is invalid.
System action
The automation manager instance will be abnormally terminated after invalidating the recovery information. This prevents a subsequent takeover or restart from attempting a retry using the invalid recovery data.
Operator response
If another automation manager instance is available, it should attempt a takeover operation, detect the invalidated restart information, and recover by attempting a warm start (see message HSAM1360I). Otherwise, the current automation manager instance will be restarted by ARM if defined by the installation as eligible for restart. If neither of these two conditions apply, manually restart the automation manager instance specifying either TYPE=WARM or TYPE=HOT.
HSAM1370I TAKEOVER WILL BE DONE FROM TAKEOVER FILE:dsn.
Explanation
The automation manager performs a hot start or a takeover from the takeover file with the name specified in dsn.
System action
None.
Operator response
None.
System programmer response
None.
HSAM1371I TAKEOVER FILE CANNOT BE READ OR IS CORRUPTED.
Explanation
The automation manager tried to read the takeover file. However, the data set is either not readable or is not a valid takeover file (does not contain a valid identifier).
System action
The automation manager continues with a warm start.
Operator response
None.
System programmer response
Check that the data set has a valid takeover file identifier. The first four bytes must contain the binary value X'12345678'.
HSAM1372I FORCE WARM START DUE TO TAKEOVER FILE OR OPERATOR RESPONSE.
Explanation
The automation manager tried to perform a hot start or a takeover from the takeover file. This action failed and the hot start was degraded to a warm start. The reason for the failure is that the operation code at offset 16 was previously set to 'W' or that it is not valid. This may occur when the previous automation manager instance has invalidated the takeover file, for example, because of an I/O problem or an internal problem.
System action
The automation manager continues with a warm start.
Operator response
None.
System programmer response
None.
HSAM1373I PROBLEM WITH TAKEOVER FILE DETECTED. REASON=rr, INFO=yyy
Explanation
The automation manager detected one of the following problems regarding the takeover:
- The reason code rr describes the problem:
- Disabled
- The previous PAM has disabled the takeover file. The takeover file might therefore be outdated.
- IOError
- The previous PAM has detected an I/O error for the takeover file. The takeover file might therefore be outdated.
- LoadError
- The previous PAM has suffered an ABEND while loading the takeover file. The most likely reason is a corrupted takeover file.
- Mismatch
- During takeover a mismatch was detected between the takeover file name in the HSAPRMxx parmlib member and the name that was used by the previous PAM.
- Possible Mismatch
- During startup of a SAM, a mismatch is detected between the takeover file name in the HSAPRMxx parmlib member and the name that was used by the previous PAM. This message might be an indication that the SAM and PAM do not use the same parmlib member HSAPRMxx. However, there is a time window where the SAM and the PAM are started concurrently where this possible mismatch can occur and can possibly be ignored. This is the case when the pending PAM has not yet finished reading the configuration file and has not yet updated the HSACFGIN accordingly. In any case it is recommended to check that the parmlib members are still valid.
- The variable yyy='tkovfile_dsn1, tkovfile_dsn2 where tkovfile_dsn1 is taken from HSAPRMxx and tkovfile_dsn2 is the takeover file that was used by the previous PAM.
System action
The automation manager also issues message HSAM1317A and waits for a response. This is not the case for reason 'Possible Mismatch'.
Operator response
Depending on the reason code, proceed as follows:
- If rr=Disabled or IOError, check that the takeover file is valid.
- If rr=Mismatch, cancel the automation manager and correct the HSAPRMxx parmlib member. See also message HSAM1317A.
- If rr=Mismatch and you decide to enter HOT, the automation manager uses the same takeover file as was used by the previous PAM rather than the takeover file name that is specified in the HSAPRMxx parmlib member.
- If rr=Mismatch and you decide to enter WARM, the automation manager that is specified in the HSAPRMxx parmlib member.
- If rr=LoadError, check if the takeover file is corrupted. If you can repair the file, then you can reply HOT to message HSAM1317A. Otherwise, continue with an Automation Manager WARM start.
HSAM1380I request REQUEST ACCEPTED.
Explanation
A request has been received and validated by the automation manager.
- The variable request shows which request was received and validated.
System action
The automation manager instance processes the request.
Operator response
None.
System programmer response
None.
HSAM1381I INVALID verb REQUEST PARAMETER, request REQUEST IGNORED.
Explanation
A parameter specified with a request is invalid for the request verb.
- The variable verb shows the request verb that one of the parameters specified on the request is invalid for.
- The variable request shows the request that could not be processed.
System action
The automation manager instance ignores the request.
Operator response
Specify valid parameters and reissue the request.
System programmer response
None.
HSAM1382I UNSUPPORTED COMMAND VERB, request REQUEST IGNORED.
Explanation
An unsupported command verb was used to route a request to the automation manager. The automation manager supports only the MVS MODIFY (F) command for request input.
- The variable request shows the request that could not be processed.
System action
The automation manager instance ignores the request.
Operator response
Contact your system programmer.
System programmer response
The automation manager command interface received the identified request with an MVS command request code other than that used for the MVS Modify command.
HSAM1383I verb REQUEST REJECTED: INCORRECT AUTOMATION MANAGER ROLE OR STATUS. INVALID verb REQUEST PARAMETER, request REQUEST IGNORED.
Explanation
An MVS MODIFY (F) command was routed to an automation manager instance that is not in a role or state compatible with the requested request verb. Because most automation manager requests run only on the primary automation manager (PAM), it is likely that the command was routed to a secondary instance. Other requests require that the target automation manager be in a "ready" state to be accepted.
- The variable verb shows the specified request verb.
- The variable request shows the request that could not be processed.
System action
The automation manager instance ignores the request.
Operator response
Verify that the command was routed to the correct automation manager instance and that the instance is in a ready state. Reissue the command accordingly
System programmer response
None.
HSAM1384I INVALID REQUEST verb, request REQUEST IGNORED. INVALID verb REQUEST PARAMETER, request REQUEST IGNORED.
Explanation
An MVS MODIFY (F) command was received with an invalid request verb.
System action
The automation manager instance ignores the request.
Operator response
Correct the verb and parameter syntax and reissue the request.
HSAM1389I BUILD ID FOR HSAPIEHM xxx yyy
Explanation
This is an information message for IBM Service. The fields xxx and yyy provide the compilation date of the event handler, for example, 2009154 152228.
System action
None.
Operator response
None.
HSAM1390E REPLY "YES" TO CONFIRM OR "NO" TO CANCEL SA z/OS AUTOMATION MANAGER STOP REQUEST.
Explanation
A conditional request has been made to stop an SA z/OS automation manager. No other SA z/OS automation manager instances are available and ready to assume automation sysplex control if this request is allowed to continue. This will result in an interruption of automation services.
System action
The SA z/OS automation manager waits for a response to this request, and continues automation sysplex control until confirmation is received.
Operator response
Reply 'YES' to terminate SA z/OS automation, 'NO' to cancel the stop request. Another SA z/OS automation manager instance may be started prior to confirming the request to avoid an interruption of automation services.
System programmer response
None.
HSAM1391E INVALID RESPONSE: REPLY "YES" TO CONFIRM OR "NO" TO CANCEL STOP REQUEST.
Explanation
An invalid response has been given to message HSAP1390E. Refer to the explanation of that message for additional information.
System action
The SA z/OS automation manager waits for a response to this request, and continues automation sysplex control until confirmation is received.
Operator response
Reply 'YES' to terminate SA z/OS automation, 'NO' to cancel the stop request. Another SA z/OS automation manager instance may be started prior to confirming the request to avoid an interruption of automation services.
System programmer response
None.
HSAM1392I AUTOMATION MANAGER STOP REQUEST CANCELLED.
Explanation
A request to confirm an automation manager stop request has been denied. Refer to the explanation of message HSAM1390E for additional information.
System action
The issuing SA z/OS automation manager continues processing.
Operator response
None.
System programmer response
None.
HSAM1393I DEFERRED STOP REQUEST WAITING FOR AUTOMATION AGENT TERMINATION.
Explanation
A deferred stop request was issued to the primary automation manager. Upon the expiration of the stop delay, one or more automation agents were active and no secondary automation manager was available to accomplish a takeover.
System action
The SA z/OS automation manager waits until all automation agents are disconnected or another automation manager instance is started.
Operator response
A deferred stop cannot be canceled. However, starting a new automation manager instance will result in the termination of the current primary manager with a takeover by that new instance.
System programmer response
None.
HSAM1396I SA z/OS AUTOMATION MANAGER SHUTDOWN IN PROGRESS, TYPE= type
Explanation
A request has been received to stop an SA z/OS automation manager instance.
- The variable type indicates the type of shutdown as requested by the initiating command.
System action
The SA z/OS automation manager instance terminates after performing cleanup activities.
Operator response
None
System programmer response
None.
HSAM1399I @1
Explanation
This is an internal message for diagnostic purposes only.
System action
None.
Operator response
None.
System programmer response
None.
HSAM5100E NO SQA STORAGE AVAILABLE.
Explanation
The first automation manager running after an IPL allocates storage in the system queue area (SQA) to hold information shared by all automation managers running on the single image and the component trace itself. This area could not be allocated.
System action
The component trace of all automation managers is disabled.
Operator response
Inform your system programmer.
System programmer response
Increase the system queue area size.
Module
HSAPICB7
HSAM5101I NUMBER OF ACTIVE AMS EXCEEDS THE NUMBER OF ASIDS SUPPORTED FOR THE COMPONENT TRACE.
Explanation
The number of active automation managers exceeds the number of address space IDs supported for the component trace. Therefore, the automation manager issuing this message did not find a free entry in the system queue area (SQA) to store its information.
System action
The automation manager’s component trace is disabled.
Operator response
None.
System programmer response
None.
Module
HSAPICB7
HSAM5102E NAME/TOKEN SERVICE FAILED. RC=rc.
Explanation
The name/token pair could not be created or deleted during initialization or termination of the automation manager.
- The variable rc shows the value of the return code that was issued.
System action
The automation manager component trace is disabled.
Operator response
None.
System programmer response
Analyze the return code (see IEANTCR/IEANTDL in z/OS MVS Assembler Service Reference).
Module
HSAPICB7, HSAPICB8
HSAM5103E MODULE module NOT FOUND.
Explanation
The automation manager component trace initialization routine could not load the required module.
- The variable module shows the name of the module that could not be loaded.
System action
If this message is followed by message HSAM5109I the component trace is disabled. Otherwise, the automation manager is terminated.
Operator response
Inform your system programmer.
System programmer response
Make the required module available to the automation manager.
Module
HSAPICB7
HSAM5104I SQA ENTRY NOT FOUND.
Explanation
The automation manager component trace termination routine could not clear its system queue area information.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPICB8
HSAM5105E DE-/REGISTRATION TO THE COMPONENT TRACE FAILED. RC=rc RSN=rsn.
Explanation
Registration to or deregistration from the component trace failed.
- The variable rc shows the return code that was issued.
- The variable rsn shows the reason code that was issued.
System action
The automation manager component trace is disabled on registration.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code and the reason code (see CTRACE in the z/OS Authorized Assembler Service Reference ).
Module
HSAPICB7, HSAPICB8
HSAM5106I ERROR OCCURRED WHEN WRITING A TRACE RECORD. POS=position, SYSTEM CC=cc.
Explanation
The PC routine writing the trace records abended with the system completion code cc.
- The variable position shows the position inside the module where the abend occurred.
- The variable cc shows the completion code.
System action
The automation manager component trace is disabled.
Operator response
Inform your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSTAR
HSAM5107I ERROR OCCURRED IN START/STOP ROUTINE. POS=position, SYSTEM CC=cc.
Explanation
The automation manager start/stop routine of the component trace abended with the system completion code cc.
- The variable position shows the position inside the module where the abend occurred.
- The variable completion_code shows the completion code.
System action
The TRACE command is not processed.
Operator response
Inform your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSTSS
HSAM5108I COMPONENT component_name ALREADY DEFINED TO THE COMPONENT TRACE.
Explanation
An automation manager could not be registered to the component trace because a previous automation manager did not deregister itself.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPICB7
HSAM5109E NAME/TOKEN SERVICE IS UNAVAILABLE.
Explanation
The MVS name/token services IEANTCR/RT/DL are not available.
System action
The automation manager component trace is disabled.
Operator response
None.
System programmer response
Make the MVS name/token service available.
Module
HSAPICB7
HSAM5110I Error occurred in display routine. Pos=position, System CC=cc.
Explanation
The automation manager display routine of the component trace abended.
- The variable position shows the position in the module where the abend occurred.
- The variable cc shows the system completion code that the display routine abended with.
System action
The TRACE command is not processed.
Operator response
Notify your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSCTD
HSAM5120E LISTENER USER EXIT INITIALIZATION FAILED. RC=rc.
Explanation
The activation of the System Logger user exit failed with a return code.
- The variable rc shows the value of the return code.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
If the return code is greater than 4, refer to the return codes of the macro ENFREQ in z/OS MVS Authorized Assembler Service Reference for further information.
Module
HSAPICB7, HSAPNCTI
HSAM5121E LISTENER USER EXIT DELETION FAILED. RC=rc.
Explanation
The deactivation of the System Logger user exit failed with a return code.
- The variable rc shows the value of the return code.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
If the return code is greater than 4, refer to the return codes of the macro ENFREQ in z/OS MVS Authorized Assembler Service Referencefor further information.
Module
HSAPICB8, HSAPNCTI
HSAM5160I VSAM request ERROR OCCURRED. RC=rc REASON=reason
Explanation
The VSAM macro instruction that corresponds to the request failed.
- The variable request shows the request that failed.
- The variable rc shows the return code that was issued.
- The variable reason shows the reason code that was issued.
System action
Processing terminates.
Operator response
Inform your system programmer.
System programmer response
Check the return and reason codes in DFSMS/MVS Macro Instructions for Data Sets, in the chapter about VSAM Macro Return and Reason Codes. Correct the error accordingly. Then rerun the program with the PARM parameter 'RERUN'.
Module
HSAPSIPL
Destination
None.
TEC: NO
HSAM5170I UNKNOWN TRACE OPTION FOUND: option
Explanation
- The variable option shows the trace option specified on the OPTIONS parameter
of the IPCS CTRACE command. The following are valid values:
- Communication
- Event
- Instruction
- Lock
- Schedule
- Workitem
System action
Processing continues.
Operator response
Correct or delete the option.
System programmer response
None.
Module
HSAPSTUE
HSAM5171I UNKNOWN KEYWORD FOUND: keyword.
Explanation
The parser found a keyword that is not valid.
- The variable keyword shows the specified filter option.
The following are valid values:
- AM
- CALLID
- ITEM
- KEY
- METHOD
- MODULE
- TASKID
System action
The keyword is ignored.
Operator response
Specify a correct keyword.
System programmer response
None.
Module
HSAPSTUE
HSAM5172I TOO MANY VALUES SPECIFIED FOR KEYWORD keyword.
Explanation
All keyword options except AM on the OPTIONS parameter support up to five different values. However, the parser found at least one additional value for keyword option keyword.
- The variable keyword shows the specified filter option.
System action
The values that exceed the number of five are ignored.
Operator response
Correct the keyword option.
System programmer response
None.
Module
HSAPSTUE
HSAM5173I N (ST/ND/RD/TH) VALUE OF KEYWORD keyword IS EMPTY.
Explanation
The parser expects a string of at least one character for the keyword option keyword on the OPTIONS parameter. However, it found no string, or a string representing the NULL string.
- The variable N shows the number of missing values.
- The variable keyword shows the specified filter option.
System action
The value is ignored.
Operator response
Correct the value.
System programmer response
None.
Module
HSAPSTUE
HSAM5174I VALUE value OF KEYWORD keyword IS NOT NUMERIC.
Explanation
The parser expects an integer for the keyword option keyword on the OPTIONS parameter. However, it found a non-numeric value.
- The variable value shows the value that is not numeric.
- The variable keyword shows the specified filter option.
System action
The value is ignored.
Operator response
Correct the value.
System programmer response
None.
Module
HSAPSTUE
HSAM5175I PARSING OF THE OPTIONS PARAMETER STOPPED AT COLUMN col.
Explanation
A column value greater than 0 indicates one of the following:
- A keyword is not spelled correctly.
- A keyword is incorrectly delimited.
- A trace option is incorrectly delimited.
A column value of 0 can be caused by one of the following:
- A parameter consisting of blanks and commas only
- A parameter length greater than 32K
- An allocation error of temporary storage
- The variable col shows which column the parser stopped at.
System action
Processing terminates.
Operator response
Correct the OPTION parameter, or increase the region size.
System programmer response
None.
Module
HSAPSTUE
HSAM5185I THE EXTERNAL WRITER HAS BEEN STARTED AUTOMATICALLY.
Explanation
The start/stop routine detected that the external writer is not active. Because the automation manager component trace requires an active external writer, the start/stop routine issued the appropriate TRACE command.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPSTSS
HSAM5186I ENVIRONMENTAL ERROR OCCURRED DURING POST OF THE LAST ACTIVE AM.
Explanation
POST of the automation manager waiting for the completion of the start/stop routine failed.
System action
Processing continues. But the automation manager is still waiting.
Operator response
Stop the automation manager manually.
System programmer response
None.
Module
HSAPSTSS
HSAM5187I PARAMETER WTR= IS MISSING.
Explanation
The start/stop routine detected that the WTR parameter is missing in the reply to the preceding TRACE command.
System action
The TRACE command is discarded.
Operator response
Re-issue the TRACE command and add the WTR parameter to the reply.
System programmer response
None.
Module
HSAPSTSS
HSAM5188I PARSING OF TRACE OPTIONS FAILED. RC=rc.
Explanation
The start/stop routine scheduled in the *MASTER* address space encountered a storage problem when parsing the OPTION parameter.
- The variable rc shows the value of the return code.
System action
The TRACE command is discarded.
Operator response
Try the command later. If the problem persists, contact your IBM Support Center.
System programmer response
None.
Module
HSAPSTSS
HSAM5189E ACCESS TO DATA SPACE FAILED. RC=rc.
Explanation
The data space where the trace records are temporarily stored could not be accessed.
- The variable rc shows the value of the return code.
System action
At least the last trace buffer is lost when the external writer is stopped.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code (see ALESERV in z/OS Authorized Assembler Service Reference).
Module
HSAPSTSS
HSAM5190E TCB TOKEN OF PARENT TASK COULD NOT BE OBTAINED. RC=rc.
Explanation
The TCB token of the parent task of the start/stop routine could not be obtained.
- The variable rc shows the value of the return code.
System action
The TRACE command is discarded.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code (see TCBTOKEN in the z/OS Authorized Assembler Service Reference).
Module
HSAPSTSS
HSAM5191I PARAMETER WTR=DISCONNECT IS NOT SUPPORTED ON A START TRACE COMMAND.
Explanation
The start/stop routine expects the name of the startup procedure of the external writer to be used. But it found the reserved word DISCONNECT.
System action
The TRACE command is discarded.
Operator response
Reissue the TRACE command and correct the WTR parameter.
System programmer response
None.
Module
HSAPSTSS
HSAM5192I INVALID TRACE OPTION SPECIFIED.
Explanation
The specified trace options could not be determined because of a parsing error.
System action
The TRACE command is rejected.
Operator response
Reissue the TRACE command and correct the OPTION parameter. Valid options are ALL or a combination of :
- [B]ase
- [COM]munication
- [CON]trol
- [EN]gine
- [EV]ent
- [F]ramework
- [HA]rdware
- [HI]story
- [I]nstruction
- [L]ock
- [M]emory
- [REQ]uest
- [REX]x
- [SCH]edule
- [SD]F
- [W]orkitem
The options must be separated by a comma.
System programmer response
None.
Module
HSAPSTSS
HSAM5193I NO TRACE OPTION SPECIFIED.
Explanation
Either the OPTION parameter was omitted, or no value was specified for it.
System action
The TRACE command is rejected.
Operator response
See message HSAM5192I for further information.
System programmer response
None.
Module
HSAPSTSS
HSAM5194I UNKNOWN TRACE OPTION FOUND: option.
Explanation
The start/stop routine found an unsupported trace option.
- The variable option shows the specified trace option.
System action
The TRACE command is rejected.
Operator response
See message HSAM5192I.
System programmer response
None.
Module
HSAPSTSS
HSAM5195E SQA HAS BEEN CORRUPTED. EYE-CATCHER=string.
Explanation
The start/stop routine detected that the system queue area has been overwritten by another task or address space.
System action
The TRACE command is discarded.
Operator response
Inform your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSTSS
HSAM5196E NAME/TOKEN token_name COULD NOT BE FOUND.
Explanation
The start/stop routine could not obtain the address of the system queue area (SQA). If the message is issued as a response to a STOP command, the data space that holds the trace buffers before they are passed to the external writer, can no longer be deleted.
- The variable token_name shows the specified token name.
System action
The TRACE command is discarded.
Operator response
Inform your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSTSS
HSAM5197E RETRIEVING NAME/TOKEN token_name FAILED. RC=rc.
Explanation
The start/stop routine encountered an error when calling the MVS service IEANTRT. If the message is issued as a response to a STOP command, the data space that holds the trace buffers before they are passed to the external writer, can no longer be deleted.
- The variable token_name shows the specified token name.
- The variable rc shows the value of the return code.
System action
The TRACE command is discarded.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code (see IEANTRT in z/OS MVS Authorized Assembler Service Reference).
Module
HSAPSTSS
HSAM5198E DATA SPACE CREATION FAILED. RC=rc RSN=rsn.
Explanation
The start/stop routine could not create the data space holding the trace buffers before they are passed to the external writer.
- The variable rc shows the value of the return code.
- The variable rsn shows the value of the reason code.
System action
The TRACE command is discarded.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code and the reason code (see DSPSERV in the z/OS MVS Authorized Assembler Service Reference).
Module
HSAPSTSS
HSAM5199I LAST TRACE BUFFER COULD NOT BE WRITTEN. RC=rc RSN=rsn.
Explanation
The start/stop routine encountered an error when writing the last trace buffer to the external writer synchronously.
- The variable rc shows the value of the return code.
- The variable rsn shows the value of the reason code.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
Analyze the return code and the reason code (see CTRACEWR in z/OS Authorized Assembler Reference).
Module
HSAPSTSS
HSAM5200E UNKNOWN KEYWORD FOUND: keyword.
Explanation
A library member (see the preceding IEE252I message) or the PARM parameter of the startup procedure contains a keyword that is not known to the automation manager.
- The variable keyword shows the value of the unknown keyword.
System action
The keyword is ignored.
Operator response
Inform your system programmer.
System programmer response
Correct or delete the keyword depending on where it is specified.
Module
HSAPSPLM
HSAM5201E INVALID KEYWORD FOUND: keyword.
Explanation
A library member (see the preceding IEE252I message) or the PARM parameter of the automation manager startup procedure contains a keyword that was not spelt correctly.
- The variable keyword shows the value of the invalid keyword.
System action
The keyword is ignored.
Operator response
Inform your system programmer.
System programmer response
Correct the keyword depending on where it is specified.
Module
HSAPSPLM
HSAM5202E INVALID KEYWORD VALUE DETECTED: KEYWORD=keyword Value=value.
Explanation
A library member (see the preceding IEE252I message) or the PARM parameter of the automation manager startup procedure contains an invalid keyword.
- The variable keyword shows the name of the keyword.
- The variable value shows the value of the invalid keyword.
System action
The keyword is ignored.
Operator response
Inform your system programmer.
System programmer response
Correct the value of the keyword depending on where it is specified.
Module
HSAPSPLM
HSAM5203E VALIDATION ROUTINE module NOT FOUND.
Explanation
A keyword validation routine could not be loaded.
- The variable module shows the name of the module.
System action
The keyword is ignored.
Operator response
Inform your system programmer.
System programmer response
Make sure that the SA z/OS library SINGLOAD is in the STEPLIB concatenation of the automation manager startup procedure and that the module is catalogued in this library.
Module
HSAPSPLM
HSAM5204E INVALID KEYWORD DETECTED AT column IN string.
Explanation
The parse service detected an invalid delimiter of a keyword. The invalid delimiter was found either in a library member (see the preceding IEE252I message) or in the PARM parameter of the automation manager startup procedure.
- The variable column shows the column where the invalid delimiter was detected.
- The variable string shows the string that contains the invalid delimiter.
System action
All keywords of the string string are ignored.
Operator response
Inform your system programmer.
System programmer response
Correct the delimiter depending on where it is specified.
Module
HSAPSPLM
HSAM5205I PROCESSING MEMBER member.
Explanation
The specified library member (see the preceding IEE252I message) is being processed.
- The variable member shows the name of the member being processed.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPSPLM
HSAM5206E MEMBER member NOT FOUND.
Explanation
The specified library member resides neither in the library concatenation of DD name HSAPLIB when this message is preceded by message IEF761I nor in the library of the PARMLIB concatenation.
- The variable member shows the name of the member that could not be found.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
Either make sure that the member is available or change the value of the keyword member to a suffix that is available. If the default member HSAPRM00 cannot be found, copy it from the SA z/OS library SINGSAMP to a library of the appropriate concatenation.
Module
HSAPSPLM
HSAM5207I PARMLIB SERVICE FAILED WHEN READING member, RC=rc Reason=rsn.
Explanation
During initialization of the automation manager the MVS PARMLIB service failed.
- The variable member shows the name of the member being processed when the MVS PARMLIB service failed.
- The variable rc shows the value of the return code.
- The variable rsn shows the value of the reason code.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
Refer to z/OS MVS Assembler Services Reference for information about the reason and return codes.
Module
HSAPSPLM
HSAM5208I INVALID STRING FOUND IN member: string.
Explanation
The parser service detected more than one keyword in a single line of a member.
- The variable member shows the name of the member where the error occurred.
System action
All keywords specified in the string are ignored.
Operator response
Inform your system programmer.
System programmer response
Correct the line in the library member member (see the preceding IEE252I message)
Module
HSAPSPLM
HSAM5209I MEMBER member TOO LARGE:
Explanation
The indicated member contains more than 10240 lines of data.
- The variable member shows the name of the member being processed using the MVS PARMLIB service.
System action
The data is truncated after line 10239.
Operator response
None.
System programmer response
None.
Module
HSAPSIPL
HSAM5210I MEMBER member EMPTY:
Explanation
The indicated member has no data.
- The variable member shows the name of the member being processed using the MVS PARMLIB service.
System action
None.
Operator response
None.
System programmer response
None.
Module
HSAPSIPL
HSAM5211I MEMBER member FOUND IN dsn.
Explanation
The indicated member has been found in the indicated data set of the PARMLIB concatenation.
- The variable member shows the name of the member being processed using the MVS PARMLIB service.
- The variable dsn shows the data set name that the member has been read from.
System action
None.
Operator response
None.
System programmer response
None.
Module
HSAPSIPL
HSAM5212E I/O ERROR READING MEMBER member.
Explanation
An I/O error occurred when trying to read the indicated PARMLIB member.
- The variable member shows the name of the member being processed using the MVS PARMLIB service.
System action
None.
Operator response
Inform your system programmer.
System programmer response
Correct the problem and re-run the program.
Module
HSAPSIPL
HSAM5213E VALUE MISSING FOR KEYWORD keyword.
Explanation
A library member (see the preceding IEE252I message) or the PARM parameter of the automation manager startup procedure contains a keyword that has no value defined.
- The variable keyword shows the name of the keyword.
System action
The keyword is ignored.
Operator response
Inform your system programmer.
System programmer response
Correct the value of the keyword depending on where it is specified.
Module
HSAPSPLM
HSAM5214I THE NEXT MESSAGES APPLY TO MEMBER member.
Explanation
The library member (see the preceding IEE252I message) contains at least one improper specification. This message is followed by further HSAM52nn messages.
- The variable member shows the name of the member being processed using the MVS parmlib service.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPSPLM
HSAM5215I THE NEXT MESSAGES APPLY TO PARM STRING.
Explanation
The PARM parameter of the startup procedure contains at least one improper specification. This message is followed by further HSAM52nn messages.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPSPLM
HSAM5300E MESSAGE MODULE module NOT FOUND.
Explanation
The automation manager initialization routine could not load the required message module.
- The variable module shows the name of the module that could not be found.
System action
The automation manager terminates.
Operator response
Inform your system programmer.
System programmer response
Make sure that the SA z/OS library SINGLOAD is the STEPLIB concatenation of the automation manager startup procedure and that the module is catalogued in this library. Then, restart the automation manager.
Module
HSAPICB9
HSAM5301E MESSAGE msgno NOT FOUND IN MODULE module.
Explanation
The message service of SA z/OS could not find the indicated message number in the message module.
- The variable msgno shows the message number that could not be found in the indicated message module.
- The variable module shows the name of the module that does not contain the indicated message number.
System action
Processing continues.
Operator response
Inform your system programmer.
System programmer response
| Module | Library | Concatenation |
|---|---|---|
| HSAAMME | SINGLINK | LNKLST |
| HSAAMLE | SINGLOAD | STEPLIB |
| INGAMYE | SINGLINK | LNKLST |
Module
HSAPSMSG
HSAM5400I logname LOG REQUEST request FAILED. RC=rc, RSN=reason.
Explanation
The request request to the log logname ended with the unexpected reason code reason.
System action
Processing continues. Depending on the reason code the affected log is marked either permanently unavailable:
- 0409
- 040A
- 080C
- 080D
- 0813
- 081A
- 081F
- 0820
- 082E
- 0843
- 0850
- 0851
- 0853
- 085D
- 0890
- 08E2
- 08E3
or temporarily unavailable:
- 0406
- 0860
- 0861
- 0862
- 0863
- 0864
- 0865
- 0867
- 0868
- 0891
Operator response
Inform your system programmer.
System programmer response
See “return and reason codes” of the related IXG... macro in z/OS MVS Authorized Assembler Service Reference for further analysis. In case the log is marked permanently unavailable and the problem can be solved, start a secondary automation manager and initiate a takeover. In addition, recycle the affected NetView(s).
Module
HSAPSSLG
HSAM5401E SYSTEM LOGGER HAS INSUFFICIENT ACCESS AUTHORITY TO log. COMPONENT TRACE.
Explanation
The system logger address space does not have access authority to the coupling facility structure associated with the log stream log.
System action
Processing continues. The log is marked permanently unavailable.
Operator response
Inform your system programmer.
System programmer response
Make sure the system logger address space has SAF access to the structure. Then, start a secondary automation manager and initiate a takeover. In addition, recycle the affected NetView(s).
Module
HSAPSSLG
HSAM5402I STRUCTURE STRNAME IS NOT DEFINED IN THE CFRM POLICY.
Explanation
The structure strname is not defined in the currently active CFRM policy.
System action
Processing continues. The log is marked permanently unavailable.
Operator response
Inform your system programmer.
System programmer response
Define the structure strname in the policy and activate the policy. Then, start a secondary automation manager and initiate a takeover. In addition, recycle the affected NetView(s).
Module
HSAPSSLG
HSAM5403I STREAM streamname IS NOT DEFINED IN THE LOGR POLICY.
Explanation
The log stream name streamname has not been defined in the LOGR policy.
System action
Processing continues. The log is marked permanently unavailable.
Operator response
Inform your system programmer.
System programmer response
Define the log stream streamname in the LOGR policy. Then, start a secondary automation manager and initiate a takeover. In addition, recycle the affected NetView(s).
Module
HSAPSSLG
HSAM5404I XES FAILED. DIAG1=XES_RC, DIAG2=XES_RSN.
Explanation
A severe cross-system extended services (XES) error has occurred.
System action
Processing continues. The affected log is marked permanently unavailable.
Operator response
Inform your system programmer.
System programmer response
Analyze the XES return code and the XES reason code.
Module
HSAPSSLG
HSAM5405I text
Explanation
The message is issued in conjunction with message HSAM5400I and reason code 081F. The reason code indicates that the system logger encountered an internal problem while processing the LOGR couple data set. The two or more messages represent the content of the 'answer area' that must be provided by each logger request.
System action
None.
Operator response
Inform your system programmer.
System programmer response
Contact your IBM Support Center.
Module
HSAPSSLG
HSAM5406I Some blocks of log logname have been deleted.
Explanation
The message is issued in conjunction with message HSAM5400I and the reason codes 0408 and 085C. To satisfy a write log request, log blocks older than six days have been deleted. The deletion is repeated day by day until the free space is large enough to satisfy the write request.
- The variable logname shows the name of the log that blocks have been deleted from.
System action
None.
Operator response
None.
System programmer response
None.
Module
HSAPSSLG
HSAM5407I logname LOG IS NOT AVAILABLE.
Explanation
The system logger address space is not available for the remainder of this IPL.
System action
Processing continues. All logs are marked permanently unavailable.
Operator response
None.
System programmer response
None.
Module
HSAPSSLG
HSAM5408I logname LOG WAS TEMPORARILY UNAVAILABLE FROM from_time TO to_time.
Explanation
While the specified log was temporarily unavailable, a WRITE request to the log had to be rejected. After the log has become available again, this message is written to the log documenting that one or more WRITE requests were not logged.
- The variable logname shows the name of the log that was not available.
- The variables from_time and to_time show the time span during which the log was not available.
System action
Processing continues.
Operator response
None.
System programmer response
None.
Module
HSAPSSLG
HSAM5409I logname LOG HAS BEEN DELETED FROM THE FIRST GAP.
Explanation
The message is issued in conjunction with message HSAM5400I and the reason codes 0402, 0403, 0836, and 084B. The log has been deleted from the first gap being detected when reading the log from the most recent data to the earliest data. One reason could be that the log stream has been defined with an incorrect VSAM share option, for example, SHR(1 3).
System action
None.
Operator response
Inform your system programmer.
System programmer response
Check and correct the VSAM definitions of the affected log stream.
Module
HSAPSSLG
HSAM5410E logname LOG REQUEST request FAILED. RC=rc, RSN=reason, Type=type.
Explanation
The request request to the log logname ended with the unexpected reason code reason.
System action
Processing continues. The log logname is marked permanently unavailable.
Operator response
Inform your system programmer.
System programmer response
Check the system log for associated IXG prefixed messages. Check the relevant zOS MVS System Messages manual for the IXG message details. If you cannot resolve the problem, contact your IBM Support Center.
Module
HSAPSSLG
HSAM5411I logname LOG HAS BEEN DELETED.
Explanation
The message is issued in conjunction with message HSAM5400I and the reason codes 0405, 0407, 0408, and 085C. The whole log must be deleted to satisfy a write log request.
System action
None.
Operator response
None.
System programmer response
None.
Module
HSAPSSLG