The AXM error recovery routine has intercepted an abend in a task running under an AXM server region TCB. The abend code is shown as three hexadecimal digits for a system completion code or four decimal digits for a user completion code. The data consists of the twelve bytes around the PSW address as provided by MVS in the SDWA.
The error recovery routine will first call AXMWH which attempts to identify the module and procedure in which the abend occurred and writes out a further message if successful. After this, if recovery is allowed, the error recovery routine terminates the affected AXM internal task and resumes normal processing, otherwise it percolates the error, causing the server region to be abnormally terminated.
The system will normally produce a symptom dump message on the job log, and a full dump may be produced if an appropriate DD statement (SYSUDUMP, SYSMDUMP or SYSABEND) is present in the server region JCL.
Look up the completion code to identify the cause of the abend.
Console and print file
AXMER
An internal logic error in a server resulted in a TRAP macro being executed at the specified location.
The system will normally produce a symptom dump message on the job log, and a full dump may be produced if an appropriate DD statement (SYSUDUMP, SYSMDUMP or SYSABEND) is present in the server region JCL.
The AXM task is abnormally terminated.
This probably indicates a logic error in server code, or an attempt to use some internal component of the server outside its correct context.
If the procedure name in the message begins with AXM, this probably indicates that the server code which called it has passed inconsistent parameters, such as an invalid address when releasing main storage.
Console and print file
AXMER
An attempt has been made to issue an operating system WAIT within an AXM server, but the server is not running on MVS. In this case, the MVS POST exit mechanism used by AXM is unavailable and operating system waits cannot be supported.
The program is abnormally terminated.
None.
Console
AXMEV
AXM server region initialization needed to define the MVS POST exit used by AXM for operating system waits, but AXM system services were not available within the current MVS image.
The server region is terminated with return code 8.
Start up AXM system services first then restart the server region. AXM system services are normally started at IPL using a subsystem definition in IEASSNxx specifying AXM as the subsystem name and AXMSI as the initialization routine. They can also be started up without an IPL by defining the subsystem dynamically using the SETSSI command.
Console and print file
AXMEV
The MVS POST exit used by AXM for operating system waits could not be created because the AXM system services routine gave a non-zero return code. The only known reason for this is that AXM system services have been withdrawn, which should not be possible in a production environment.
The server region is terminated with return code 8.
None.
Console and print file
AXMEV
During server initialization, AXM system services found that the MVS POST exit used by AXM for operating system waits had already been created for this address space. AXM therefore bypassed trying to create the same POST exit again as this would have resulted in an abend 702-04.
This can occur when a previous server execution in the same address space was terminated abnormally.
Processing continues
None.
Console and print file
AXMEV
The MVS POST exit used by AXM for operating system waits could not be deleted because the AXM system services routine gave a non-zero return code. The only known reason for this is that AXM system services have been withdrawn, which should not be possible in a production environment.
Processing continues.
None.
Console.
AXMEV
AXM initialization has detected that the total link-edited size of the pseudo-register vector (PRV) for the server application load module exceeds the maximum size of 4096 supported by AXM. The PRV contains task-related variables used by AXM resource management plus any task-related data areas defined by server code using the Assembler DXD operation code or Q-type address constants.
The server is abnormally terminated.
The server programmer needs to decrease the size of task-related variables defined in the PRV. When a large amount of task-related information needs to be stored, it is better to store the information in some separately acquired storage area (such as AXM heap storage) and put only a pointer to it in the PRV.
Console
AXMLF
An AXM server program attempted to acquire exclusive ownership of an AXM lock which was already in shared ownership for the current task. This is not allowed, as the task cannot wait for itself.
The AXM lock request is rejected.
The server programmer needs to modify the program logic. It could for example use an AXM lock PROMOTE to convert the shared lock to an exclusive lock.
Console and print file
AXMLK
An AXM server program tried to release, demote or promote an AXM lock but the lock was not owned by the current AXM task.
The AXM lock request is rejected.
The server program logic is in error.
Console and print file
AXMLK
This message is written to the print file during AXM initialization to indicate the name and entry point address of the server main procedure. This is primarily for debugging purposes.
Processing continues.
None.
Print file
AXMOS
The AXM server load module which is being executed does not contain a procedure which has been identified as the AXM main procedure.
The server region is terminated with return code 16.
Check that the main procedure was correctly included in the link edit. If it was, make sure that its entry point name was correctly specified on the END statement and that it was assembled using AXM macros with the macro AXMSET appearing before the MODULE statement and the option ENVIRON=AXM specified on the MODULE statement.
Console and SYSPRINT
AXMOS
This message is written to the print file during AXM initialization to indicate the size of the largest area of 31-bit addressable private region storage available at that time.
Processing continues.
None.
Print file
AXMPG
This message is written to the print file during AXM initialization to indicate the size of the largest area of 24-bit addressable private region storage available at that time.
Processing continues.
None.
Print file
AXMPG
This message is written to the print file during AXM initialization to show the size and address of each storage page pool as it is created. Once this has been done, most AXM storage requests are allocated from this page pool rather than with MVS GETMAIN.
Processing continues.
None.
Print file
AXMPG
This message shows statistics for the named storage page pool (since the most recent statistics reset, if any). It is automatically written to the print file at AXM region termination, and may also be requested at other times by the server.
The detailed message layout is as follows:
Size In Use Max Used Free Min Free
nK nK nK nK nK
100% n% n% n% n%
Gets Frees Retries Fails
n n n n
Each of the storage statistics is shown in two forms, as a number of kilobytes and as a percentage of the total size.
The individual fields have the following meanings:
Processing continues.
None.
Print file
AXMPG
A server routine established an AXM resource tracking element specifying that a procedure was to be called to release the resource if the task was terminated without releasing the resource. The AXM task is now terminating, and the procedure identified in the tracking element was called, but the resource tracking element was still in existence when it returned. The entry point address of the relevant procedure is indicated in the message.
The tracking element is released on the assumption that the resource has now been deleted, and AXM task termination continues.
The server programmer needs to ensure that the procedure to release the resource also frees the resource tracking element.
Console and print file
AXMRS
AXM system services are being started up, normally as a result of being called by the AXM subsystem initialization routine.
Processing continues.
None.
Console
AXMSC
AXM system services are now fully available in the current MVS image.
AXM cross-memory server connection requests and requests for the POST exit system services will now be accepted.
None.
Console
AXMSC
An attempt was made to set up AXM system services again when they are already active in the current MVS image.
The attempt is ignored.
None.
Console
AXMSC
AXM system services are being withdrawn. This is only possible if they were initialized using the AXM system region program AXMSR instead of being set up via subsystem initialization.
The AXM system services program call table is deleted and all entry points in the AXM system services anchor are replaced with dummy routines which return an indication that the service are not available.
Note that the results of attempting to call any AXM system service around this time are unpredictable. AXM system services should never be withdrawn in a production environment at any time when it is possible that they could be in use.
Console
AXMSC
AXM system services have been closed down for this MVS image.
AXM system services are no longer available.
None.
Console
AXMSC
The current region has established an AXM connection to the AXM server prefix.name.
Processing continues.
None.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but could not do so because there is no active server of that name enabled for AXM connections.
The connection attempt is rejected with return code 8, reason code 32.
Ensure that the server is started and that its name was specified correctly.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but the request was rejected by the security system.
The connection attempt is rejected with return code 8, reason code 33.
See the previous AXM message giving details of the results of the security check.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but the maximum number of AXM connections supported within an MVS image (currently 4096) has been reached.
The connection is rejected with return code 8, reason code 34.
If you anticipate a need for more than 4096 AXM server connections within a single MVS image, you will need assistance from IBM. See Part 4 of the CICS® Problem Determination Guide for guidance on how to proceed.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but the connection parameter specifying the maximum number of concurrent requests to be supported exceeds 9999.
The connection is rejected with return code 8, reason code 35.
Check whether the server interface program is specifying the correct value for the maximum number of concurrent requests.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but the server-defined connection exit rejected the request.
The connection is rejected with return code 8, reason code 36.
The reason for the rejection depends on the server code, but this typically occurs if the server is preparing to close down or has insufficient resources to accept another connection.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but the server entered termination processing while the connection request was in progress.
The connection is rejected with return code 8, reason code 37. The instance of the server that was being terminated will no longer be visible to any new connection attempts.
Retry the connection when the server has been restarted.
Console
AXMSC
The current region tried to establish an AXM connection to the AXM server prefix.name but it already has a connection to the same server region. AXM does not support multiple connections from the same region to the same server region.
The connection is rejected with return code 8, reason code 38.
None.
Console
AXMSC
An AXM connection from the current region to the named server has been terminated, either as a result of being explicitly closed by this region or as a result of the termination of the MVS TCB which originally established the connection.
Processing continues.
None.
Console
AXMSC
An attempt was made to close an AXM connection explicitly but the specified connection token did not refer to an active connection owned by the current region, or the connection could not be closed for some other reason.
The reason code indicates which validity check failed within procedure AXMSCCLS. Reason code 9 indicates that a request issued via the connection has not yet completed. Any other reason code probably indicates an incorrect token.
The attempt is rejected with return code 8, reason code 42.
Check that the connection close request is specifying the correct connection token and that there are no incomplete requests for the connection.
Console
AXMSC
This AXM server has completed initialization and is now available for connections from other address spaces.
Processing continues.
None.
Console
AXMSC
Only one instance of a given AXM server name can be active in an MVS image at a time.
The attempt to enable the server interface is rejected with return code 8, reason code 52.
None.
Console
AXMSC
AXM requires that an AXM server region must be running APF authorized in order to be allowed to enable its server interface.
The attempt to enable the server interface is rejected with return code 8, reason code 53.
Ensure that the server program is executed from an APF authorized library and is link-edited with AC(1).
Console
AXMSC
The security system detected that the server region userid was not correctly authorized to act as an AXM server with the specified server name.
The attempt to enable the server interface is rejected with return code 8, reason code 54.
See the previous AXM message giving details of the results of the security check.
Console
AXMSC
This AXM server is terminating and is no longer available for connections from other address spaces. This occurs either when the server explicitly disables its interface or when the server job step task terminates.
Processing continues.
None.
Console
AXMSC
An attempt to disable the server interface failed because the specified server interface token did not correctly identify an active server interface established by the current address space.
The reason code provides an internal indication of which validity check failed within procedure AXMSCDIS. All reason codes probably indicate an incorrect token.
The attempt to disable the server interface is rejected with return code 8, reason code 62. If the server interface is still enabled, it will be disabled automatically when the job step task terminates.
As the server interface token is stored internally by AXM, the only known possible reason for this message is storage overwriting within the server region.
Console
AXMSC
AXM requires that an AXM server region must be running APF authorized in order to be allowed to disable its server interface.
The attempt to disable the server interface is rejected with return code 8, reason code 63.
Ensure that the server program is executed from an APF authorized library and is link-edited with AC(1).
Console
AXMSC
The security checking routine has detected that the AXM server name specified on a connection request or on a server enable request is not in the correct form, for example because either the prefix or name is blank. This means that the security check cannot be performed.
A return code is set to indicate that the security check failed.
Check that the server prefix and name are specified correctly. The prefix is normally defined by the server, but the name may be set from a user-specified server parameter.
Console
AXMSC
The external security manager has indicated that the current region is not authorized for the required level of access to the specified facility.
A return code is set to indicate that the security check failed.
Check whether the userid for the region has been authorized to access the specified facility resource name.
Console
AXMSC
The external security manager has indicated that it is unable to determine whether the current region is authorized for the required level of access to the specified facility. This message is only issued if it is not possible for the security routine to determine whether security checking is actually required. In cases where it is obvious that no security check is required (for example because no external security manager is installed), access is granted anyway.
A return code is set to indicate that the security check failed.
Check whether the external security manager is available and whether the security definitions for the specified facility have been provided.
Console
AXMSC
This message provides additional details about the results of a security check in any case where access is not granted. See the documentation of the RACROUTE macro for further information.
Processing continues.
None.
Console
AXMSC
This message provides additional details about the results of a security check in any case where access is not granted. See the documentation of the RACROUTE macro for further information.
Processing continues.
None.
Console
AXMSC
This message is issued during AXM system services initialization to enable the system services anchor to be located if necessary for diagnostic purposes.
AXM system services initialization processing continues.
None.
Console
AXMSC
This message is issued during AXM system services initialization if AXM system services were previously active but had been terminated (which is not possible in normal production environment). The old system services anchor is retained after AXM termination because it contains the system LX to be used if AXM is restarted. This message gives the address of the old system services anchor for diagnostic purposes.
AXM system services initialization processing continues.
None.
Console
AXMSC
The AXM subsystem initialization program has been started in order to initialize AXM system services.
AXM system services will be loaded and initialized.
None.
Console
AXMSI
The AXM subsystem initialization program has completed execution.
The program returns control to MVS.
None.
Console
AXMSI
The AXM subsystem initialization routine has not completed normally. This message indicates the final return code and reason code. This is normally the return code from AXM system services initialization.
The subsystem initialization routine returns control to MVS.
See the previous AXM message describing the cause of the problem. The reason code will normally be the number of an error message issued by AXMSC.
Console
AXMSI
An attempt has been made to invoke the AXM subsystem initialization program AXMSI in some other way than as an MVS subsystem initialization program running in the Master Scheduler region (ASID 0001).
The subsystem initialization program is abnormally terminated.
None.
Console
AXMSI
An AXM system region is being started. This is used to initialize AXM system services in a testing environment for development purposes, and allows AXM system services to be closed down and restarted without an IPL.
Processing continues.
None.
Console
AXMSR
AXM system services have been successfully initialized from the AXM system region.
Processing continues.
The system region may be closed down again using the MVS STOP command but this should only be done when it is certain that no AXM services are being used within the MVS image.
Console
AXMSR
The operator has requested termination of the AXM system region using the MVS STOP command.
AXM system services are terminated.
None.
Console
AXMSR
The AXM system region has completed termination.
Control is returned to MVS and the job step ends.
None.
Console
AXMSR
An attempt was made to execute the AXM system region program AXMSR in a non-MVS environment.
The system region program terminates.
None.
Console
AXMSR
An attempt was made to execute the AXM system region program AXMSR without APF authorization.
The system region program terminates.
Ensure that the module AXMSR is stored in an APF-authorized library and is link-edited with AC(1).
Console
AXMSR
The attempt to LOAD the system services module (AXMSC) failed.
The system region program terminates.
See the description of the system completion code xxx in MVS/ESA System Codes for the reason that the LOAD failed.
Console
AXMSR
An attempt was made to issue a command to the AXM system region using the MVS MODIFY command. The AXM system region only supports the MVS STOP command, and does not support commands entered via MODIFY.
The command is ignored.
If the intention was to close down the system region, use the MVS STOP command instead.
Console
AXMSR
An operator has issued a STOP command to close down the AXM system region.
AXM system services will be terminated.
None.
Console
AXMSR
The AXM trace and print file with the specified ddname (usually AXMPRINT or SYSPRINT) could not be opened during AXM initialization.
Print file output requests will be ignored.
Ensure that the appropriate DD statement is present. The default ddname is AXMPRINT, but this may be overridden to SYSPRINT by an AXMTRDEF definition within the server code if the server does not need to reserve the name SYSPRINT for any other purpose.
Console
AXMTR
This message may be produced after an abend or TRAP message to identify the module containing the error address, if the module is known to MVS. The information about the module and type is obtained using the MVS macros CSVQUERY or NUCLKUP.
Processing continues.
None.
Console and print file
AXMWH
This message may be produced after an abend or TRAP message to identify the procedure containing the error address, if the storage is within a known module and a standard SAVE sequence including a procedure identifier appears at some point before the error address.
Processing continues.
None.
Console
AXMWH
An attempt has been made to enable a server interface but AXM system services have not been initialized within this MVS image.
The server enable request is rejected.
Ensure that AXM system services are started then start the server again.
Console and SYSPRINT
AXMXM
The server interface could not be enabled. The specific reason will have been indicated by an earlier AXMSC message.
The server enable request is rejected.
None.
Console and SYSPRINT
AXMXM
The ARR routine for an AXM cross-memory program call routine has intercepted an abend in a cross-memory mode AXM task and has passed the associated SDWA to a task in the server address space to issue the appropriate diagnostic messages. The abend code is shown as three hexadecimal digits for a system completion code or four decimal digits for a user completion code. The data consists of the twelve bytes around the PSW address as provided by MVS in the SDWA.
The ARR will already have completed processing when this message is issued, as the message is written out by the server region. If recovery is allowed, the ARR terminates the affected AXM internal task, in which case the return code from the cross-memory request will consist of the completion code in the usual MVS format but with the high-order bit set to indicate an abend. If recovery is not allowed, the ARR percolates the error, passing the abend to the requesting region.
The diagnostic routine which writes this message will call AXMWH which attempts to identify the module and procedure in which the abend occurred and writes out a further message if successful. It then releases the MVS SDWA. Server execution is not directly affected by an abend in cross-memory mode.
Look up the completion code to identify the cause of the abend.
Console and SYSPRINT
AXMXM
An internal logic error in a server module or invalid parameters on a server request resulted in a TRAP macro being executed at the specified location in cross-memory mode.
The system will normally produce a symptom dump message on the job log, and a full dump of the connected region may be produced if an appropriate DD statement (SYSUDUMP, SYSMDUMP or SYSABEND) is present in the JCL for the connected region.
The AXM task is abnormally terminated.
This probably indicates a logic error in server code, or an attempt to use some internal component of the server outside its correct context.
If the procedure name in the message begins with AXM, this probably indicates that the server code which called it has passed inconsistent parameters, such as an invalid address when releasing main storage.
Console
AXMXM