REQTEXT

AXM error recovery messages

AXMER0001
ABEND xxx-rr occurred at address, data word1 word2 word3.
Explanation:

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.

System action:

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.

User response:

Look up the completion code to identify the cause of the abend.

Destination:

Console and print file

Module:

AXMER

AXMER0002
TRAP occurred at offset offset in procname.
Explanation:

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.

System action:

The AXM task is abnormally terminated.

User response:

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.

Destination:

Console and print file

Module:

AXMER

AXM event management messages

AXMEV0001
AXM only supports operating system WAIT on MVS.
Explanation:

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.

System action:

The program is abnormally terminated.

User response:

None.

Destination:

Console

Module:

AXMEV

AXMEV0003
The AXM POST exit could not be created because AXM system services are not available.
Explanation:

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.

System action:

The server region is terminated with return code 8.

User response:

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.

Destination:

Console and print file

Module:

AXMEV

AXMEV0004
The AXM POST exit could not be created, return code was rc.
Explanation:

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.

System action:

The server region is terminated with return code 8.

User response:

None.

Destination:

Console and print file

Module:

AXMEV

AXMEV0005I
The AXM POST exit had already been created for this address space.
Explanation:

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.

System action:

Processing continues

User response:

None.

Destination:

Console and print file

Module:

AXMEV

AXMEV0006I
The AXM POST exit could not be deleted, return code was rc.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console.

Module:

AXMEV

AXM stack (LIFO) storage messages

AXMLF0001S
LIFO storage cannot be set up because the PRV size exceeds 4K.
Explanation:

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.

System action:

The server is abnormally terminated.

User response:

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.

Destination:

Console

Module:

AXMLF

AXM lock management messages

AXMLK0001
Lock at address is already owned for shared use by this task.
Explanation:

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.

System action:

The AXM lock request is rejected.

User response:

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.

Destination:

Console and print file

Module:

AXMLK

AXMLK0002
function failed because lock at address is not owned by this task.
Explanation:

An AXM server program tried to release, demote or promote an AXM lock but the lock was not owned by the current AXM task.

System action:

The AXM lock request is rejected.

User response:

The server program logic is in error.

Destination:

Console and print file

Module:

AXMLK

AXM operating system interface messages

AXMOS0001I
The main procedure entry point is name at address address.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Print file

Module:

AXMOS

AXMOS0002
The main procedure is missing, or the END statement does not name the entry point.
Explanation:

The AXM server load module which is being executed does not contain a procedure which has been identified as the AXM main procedure.

System action:

The server region is terminated with return code 16.

User response:

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.

Destination:

Console and SYSPRINT

Module:

AXMOS

AXM storage page pool management messages

AXMPG0001I
The main free area above 16M was at address xxxxxx, size nnnnK.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Print file

Module:

AXMPG

AXMPG0002I
The main free area below 16M was at address xxxxxx1, size nnnnK.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Print file

Module:

AXMPG

AXMPG0003I
Storage page pool areaname created, address xxxxxx, size nnnnK.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Print file

Module:

AXMPG

AXMPG0004I
Usage statistics for storage page pool areaname:
Explanation:

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:

Size
Total size of the storage pool.
In Use
The amount of storage which is currently in use.
Max Used
The highest amount of storage which has been in use.
Free
The amount of storage within the pool which is current free.
Min Free
The lowest amount of storage which has been free.
Gets
The number of requests to obtain storage within the pool.
Frees
The number of requests to release storage within the pool.
Retries
The number of times that a storage request initially failed and was retried after merging any adjacent small free areas to form larger areas.
Fails
The number of times that a storage request was unable to obtain the requested amount of storage even after a retry.
System action:

Processing continues.

User response:

None.

Destination:

Print file

Module:

AXMPG

AXM resource tracking messages

AXMRS0001
Tidy-up routine at address failed to free resource tracking cell.
Explanation:

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.

System action:

The tracking element is released on the assumption that the resource has now been deleted, and AXM task termination continues.

User response:

The server programmer needs to ensure that the procedure to release the resource also frees the resource tracking element.

Destination:

Console and print file

Module:

AXMRS

AXM server connection and system services messages

AXMSC0011I
AXM system services initialization is in progress.
Explanation:

AXM system services are being started up, normally as a result of being called by the AXM subsystem initialization routine.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0012I
AXM system services initialization has completed.
Explanation:

AXM system services are now fully available in the current MVS image.

System action:

AXM cross-memory server connection requests and requests for the POST exit system services will now be accepted.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0013
AXM system services have already been initialized.
Explanation:

An attempt was made to set up AXM system services again when they are already active in the current MVS image.

System action:

The attempt is ignored.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0021I
AXM system services termination is in progress.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Module:

AXMSC

AXMSC0022I
AXM system services termination has completed.
Explanation:

AXM system services have been closed down for this MVS image.

System action:

AXM system services are no longer available.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0031I
Connection to server prefix.name has been opened.
Explanation:

The current region has established an AXM connection to the AXM server prefix.name.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0032
Connection to server prefix.name failed because the server was not found.
Explanation:

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.

System action:

The connection attempt is rejected with return code 8, reason code 32.

User response:

Ensure that the server is started and that its name was specified correctly.

Destination:

Console

Module:

AXMSC

AXMSC0033
Connection to server prefix.name was rejected by the security system.
Explanation:

The current region tried to establish an AXM connection to the AXM server prefix.name but the request was rejected by the security system.

System action:

The connection attempt is rejected with return code 8, reason code 33.

User response:

See the previous AXM message giving details of the results of the security check.

Destination:

Console

Module:

AXMSC

AXMSC0034
Connection to server prefix.name failed because all AXM connections are in use.
Explanation:

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.

System action:

The connection is rejected with return code 8, reason code 34.

User response:

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.

Destination:

Console

Module:

AXMSC

AXMSC0035
Connection to server prefix.name failed because request limit reqs exceeds 9999.
Explanation:

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.

System action:

The connection is rejected with return code 8, reason code 35.

User response:

Check whether the server interface program is specifying the correct value for the maximum number of concurrent requests.

Destination:

Console

Module:

AXMSC

AXMSC0036
Connection to server prefix.name was rejected by the server.
Explanation:

The current region tried to establish an AXM connection to the AXM server prefix.name but the server-defined connection exit rejected the request.

System action:

The connection is rejected with return code 8, reason code 36.

User response:

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.

Destination:

Console

Module:

AXMSC

AXMSC0037
Connection to server prefix.name failed because the server is terminating.
Explanation:

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.

System action:

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.

User response:

Retry the connection when the server has been restarted.

Destination:

Console

Module:

AXMSC

AXMSC0038
Connection to server prefix.name failed because this address space is already connected to it.
Explanation:

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.

System action:

The connection is rejected with return code 8, reason code 38.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0041I
Connection to server prefix.name has been closed.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0042
Connection close failed for token xxxxxxxx, reason is n.
Explanation:

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.

System action:

The attempt is rejected with return code 8, reason code 42.

User response:

Check that the connection close request is specifying the correct connection token and that there are no incomplete requests for the connection.

Destination:

Console

Module:

AXMSC

AXMSC0051I
Server prefix.name is now enabled for connections.
Explanation:

This AXM server has completed initialization and is now available for connections from other address spaces.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0052
Server prefix.name cannot be enabled because it is already active in another address space.
Explanation:

Only one instance of a given AXM server name can be active in an MVS image at a time.

System action:

The attempt to enable the server interface is rejected with return code 8, reason code 52.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0053
Server prefix.name cannot be enabled because caller is not APF authorized.
Explanation:

AXM requires that an AXM server region must be running APF authorized in order to be allowed to enable its server interface.

System action:

The attempt to enable the server interface is rejected with return code 8, reason code 53.

User response:

Ensure that the server program is executed from an APF authorized library and is link-edited with AC(1).

Destination:

Console

Module:

AXMSC

AXMSC0054
Server prefix.name cannot be enabled because the security system rejected the request.
Explanation:

The security system detected that the server region userid was not correctly authorized to act as an AXM server with the specified server name.

System action:

The attempt to enable the server interface is rejected with return code 8, reason code 54.

User response:

See the previous AXM message giving details of the results of the security check.

Destination:

Console

Module:

AXMSC

AXMSC0061I
Server prefix.name is now disabled for connections.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0062
Server disable failed for token xxxxxxxx, reason is n.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Module:

AXMSC

AXMSC0063
Server prefix.name cannot be disabled because caller is not APF authorized.
Explanation:

AXM requires that an AXM server region must be running APF authorized in order to be allowed to disable its server interface.

System action:

The attempt to disable the server interface is rejected with return code 8, reason code 63.

User response:

Ensure that the server program is executed from an APF authorized library and is link-edited with AC(1).

Destination:

Console

Module:

AXMSC

AXMSC0071
Server name prefix.name has incorrect syntax for access checks.
Explanation:

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.

System action:

A return code is set to indicate that the security check failed.

User response:

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.

Destination:

Console

Module:

AXMSC

AXMSC0072
level access authorization was denied for FACILITY facility.
Explanation:

The external security manager has indicated that the current region is not authorized for the required level of access to the specified facility.

System action:

A return code is set to indicate that the security check failed.

User response:

Check whether the userid for the region has been authorized to access the specified facility resource name.

Destination:

Console

Module:

AXMSC

AXMSC0073
level access authorization is unavailable for FACILITY facility.
Explanation:

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.

System action:

A return code is set to indicate that the security check failed.

User response:

Check whether the external security manager is available and whether the security definitions for the specified facility have been provided.

Destination:

Console

Module:

AXMSC

AXMSC0074
RACROUTE REQUEST=AUTH gave R15=xxxxxxxx, SAFPRRET=xxxxxxxx, SAFPRREA=xxxxxxxx.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0075
RACROUTE REQUEST=STAT gave R15=xxxxxxxx, SAFPRRET=xxxxxxxx, SAFPRREA=xxxxxxxx.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0991I
Creating new AXM system services anchor at address.
Explanation:

This message is issued during AXM system services initialization to enable the system services anchor to be located if necessary for diagnostic purposes.

System action:

AXM system services initialization processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXMSC0992I
Deleting old AXM system services anchor at address.
Explanation:

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.

System action:

AXM system services initialization processing continues.

User response:

None.

Destination:

Console

Module:

AXMSC

AXM subsystem initialization messages

AXMSI0001I
AXM subsystem initialization is in progress.
Explanation:

The AXM subsystem initialization program has been started in order to initialize AXM system services.

System action:

AXM system services will be loaded and initialized.

User response:

None.

Destination:

Console

Module:

AXMSI

AXMSI0002I
AXM subsystem initialization has completed.
Explanation:

The AXM subsystem initialization program has completed execution.

System action:

The program returns control to MVS.

User response:

None.

Destination:

Console

Module:

AXMSI

AXMSI0003
AXM subsystem initialization return code retcode, reason code rsncode.
Explanation:

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.

System action:

The subsystem initialization routine returns control to MVS.

User response:

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.

Destination:

Console

Module:

AXMSI

AXMSI0004
AXM subsystem initialization can only run in Master Scheduler address space.
Explanation:

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).

System action:

The subsystem initialization program is abnormally terminated.

User response:

None.

Destination:

Console

Module:

AXMSI

AXM system region messages

AXMSR0001I
AXM system region initialization is in progress.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMSR

AXMSR0002I
AXM system region initialization has completed.
Explanation:

AXM system services have been successfully initialized from the AXM system region.

System action:

Processing continues.

User response:

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.

Destination:

Console

Module:

AXMSR

AXMSR0003I
AXM system region termination is in progress.
Explanation:

The operator has requested termination of the AXM system region using the MVS STOP command.

System action:

AXM system services are terminated.

User response:

None.

Destination:

Console

Module:

AXMSR

AXMSR0004I
AXM system region termination has completed.
Explanation:

The AXM system region has completed termination.

System action:

Control is returned to MVS and the job step ends.

User response:

None.

Destination:

Console

Module:

AXMSR

AXMSR0011
AXM system region can only run under MVS/ESA.
Explanation:

An attempt was made to execute the AXM system region program AXMSR in a non-MVS environment.

System action:

The system region program terminates.

User response:

None.

Destination:

Console

Module:

AXMSR

AXMSR0012
AXM system region program AXMSR needs to be APF authorized.
Explanation:

An attempt was made to execute the AXM system region program AXMSR without APF authorization.

System action:

The system region program terminates.

User response:

Ensure that the module AXMSR is stored in an APF-authorized library and is link-edited with AC(1).

Destination:

Console

Module:

AXMSR

AXMSR0013
AXM system region LOAD for name failed with completion code xxx-nn.
Explanation:

The attempt to LOAD the system services module (AXMSC) failed.

System action:

The system region program terminates.

User response:

See the description of the system completion code xxx in MVS/ESA System Codes for the reason that the LOAD failed.

Destination:

Console

Module:

AXMSR

AXMSR0021
AXM system region does not support this command: text
Explanation:

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.

System action:

The command is ignored.

User response:

If the intention was to close down the system region, use the MVS STOP command instead.

Destination:

Console

Module:

AXMSR

AXMSR0022I
AXM system region STOP command has been accepted.
Explanation:

An operator has issued a STOP command to close down the AXM system region.

System action:

AXM system services will be terminated.

User response:

None.

Destination:

Console

Module:

AXMSR

AXM trace and print file management messages

AXMTR0001
The ddname print file could not be opened.
Explanation:

The AXM trace and print file with the specified ddname (usually AXMPRINT or SYSPRINT) could not be opened during AXM initialization.

System action:

Print file output requests will be ignored.

User response:

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.

Destination:

Console

Module:

AXMTR

AXM address lookup (WHERE) messages

AXMWH0001I
Address address is at +offset in modtype module modname.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console and print file

Module:

AXMWH

AXMWH0002I
Address address is at +offset in procedure procname.
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

Console

Module:

AXMWH

AXM cross-memory interface messages

AXMXM0011
Server prefix.name cannot be enabled because AXM system services are not available.
Explanation:

An attempt has been made to enable a server interface but AXM system services have not been initialized within this MVS image.

System action:

The server enable request is rejected.

User response:

Ensure that AXM system services are started then start the server again.

Destination:

Console and SYSPRINT

Module:

AXMXM

AXMXM0012
Enable failed for server prefix.name, return code retcode, reason rsncode.
Explanation:

The server interface could not be enabled. The specific reason will have been indicated by an earlier AXMSC message.

System action:

The server enable request is rejected.

User response:

None.

Destination:

Console and SYSPRINT

Module:

AXMXM

AXMXM0021
ABEND xxx-rr occurred at address, data word1 word2 word3.
Explanation:

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.

System action:

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.

User response:

Look up the completion code to identify the cause of the abend.

Destination:

Console and SYSPRINT

Module:

AXMXM

AXMXM0022
TRAP occurred at offset offset in procname.
Explanation:

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.

System action:

The AXM task is abnormally terminated.

User response:

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.

Destination:

Console

Module:

AXMXM

[[ Contents Previous Page | Next Page Index ]]