DFHSMxxxx messages

DFHSM0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHSMAD, DFHSMAR, DFHSMCK, DFHSMDM, DFHSMGF, DFHSMMCI, DFHSMMC2, DFHSMMF, DFHSMMG, DFHSMPQ, DFHSMPP, DFHSMSR, DFHSMST, DFHSMSU, DFHSMSY

XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname

DFHSM0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

Start of changeSee the CICS Trace Entries for a description of the exception trace point ID, X'code' and the data it contains.End of change

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHSMAD, DFHSMAR, DFHSMCK, DFHSMGF, DFHSMMC2, DFHSMMF, DFHSMMG, DFHSMPQ, DFHSMPP DFHSMSCP, DFHSMSR, DFHSMST, DFHSMSU, DFHSMSY

XMEOUT Parameters: applid, X'code',modname

DFHSM0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of processor time, this message may have been caused by a long-running function. So there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that module modname in the message is terminated and CICS continues.

But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently. But you can change the ICVR time interval temporarily online, using the CEMT transaction.

If raising the ICVR time does not solve the problem, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHSMMCI, DFHSMST

XMEOUT Parameters: applid, X'offset', modname

DFHSM0006
applid Insufficient storage to satisfy Getmain (code X'code') in module modname. MVS code mvscode.
Explanation:

An MVS GETMAIN was issued by module modname, but there was insufficient storage available to satisfy the request.

The code X'code' is the exception trace point ID which uniquely identifies the place where the error was detected.

The code mvscode is the MVS GETMAIN return code.

System action:

An exception entry is made in the trace table (code X'code'). A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

If CICS has been terminated by another module, look out for the relevant termination messages (from, for example, the domain manager), and look up the user response suggested for these messages.

If CICS is still running, the problem may be a temporary one which rights itself if more storage becomes available. If you can manage without module modname, you may decide to continue and bring CICS down at a convenient time to resolve the problem. If the message recurs or if you cannot run without the full use of all CICS modules, you should bring CICS down in a controlled shutdown.

Start of changeSee the CICS Trace Entries for a description of the exception trace point ID, X'code' and the data it contains.End of change

You can get diagnostic information about the MVS return code by consulting the relevant MVS codes manual.

Try decreasing the limits of the CICS dynamic storage areas (DSAs), or increasing the MVS region size. You can vary the CICS DSAs dynamically using the DSALIM and EDSALIM parameters on the CEMT master terminal command. To increase the MVS region size you must bring CICS down and change the MVS JCL REGION parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, X'code',modname, mvscode

DFHSM0102
applid A storage violation (code X'code') has been detected by module modname.
Explanation:

A storage violation has been detected by module modname. The code X'code' is the exception trace point ID which uniquely identifies the type of storage violation.

System action:

Start of changeAn exception entry (X'code' in the message) is made in the trace table. Use the exception trace point ID, X'code', to investigate the cause of the storage violation. A description of the exception trace point ID, and the data it contains, is in the CICS Trace Entries.End of change A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

If you have enabled storage recovery (by specifying the system initialization parameter STGRCVY=YES), CICS attempts to repair the storage violation. Otherwise, the storage is left unchanged.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Start of changeUse the exception trace point ID, X'code', to investigate the cause of the storage violation. See the CICS Trace Entries for a description of the exception trace point ID and the data it contains.End of change

Destination:

Console

Modules:

DFHSMAR, DFHSMCK, DFHSMGF, DFHSMMC2, DFHSMMF

XMEOUT Parameters: applid, X'code',modname

DFHSM0103
applid A storage violation (code X'code') has been detected by the storage violation trap. Trap is now inactive.
Explanation:

A storage violation has been detected by the storage violation trap, which may be enabled via the CHKSTSK or the CHKSTRM system initialization parameters or via the CSFE transaction. The code X'code' is the exception trace point ID which uniquely identifies the type of storage violation detected.

System action:

CICS disables the storage violation trap. An exception entry (X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

If you have enabled storage recovery (by specifying the system initialization parameter STGRCVY=YES), CICS attempts to repair the storage violation. Otherwise, the storage is left unchanged.

Message DFHME0116 is normally produced containing the symptom string for this problem.

Note:
Even if CICS is able to repair the storage, the storage violation trap still remains inactive.
User response:

Start of changeUse the exception trace point ID, X'code', to investigate the cause of the storage violation. See the CICS Trace Entries for a description of the exception trace point ID and the data it contains.End of change

Destination:

Console

Modules:

DFHSMCK

XMEOUT Parameters: applid, X'code'

DFHSM0113I
applid Storage protection is not active.
Explanation:

This is an informatory message stating that storage protection has not been requested (STGPROT=NO) and is not in effect for this execution of CICS.

System action:

CICS continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0. Storage protection can be enabled by specifying the system initialization parameter STGPROT=YES.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0114
applid Storage protection was requested but the support is not available. Storage protection is not active.
Explanation:

This is an informatory message stating that although storage protection was requested, it is not in effect for this execution of CICS because the necessary hardware and/or operating system support is not available.

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0115I
applid Storage protection is active.
Explanation:

This is an informatory message stating that storage protection is requested (STGPROT=YES) and is in effect for this execution of CICS.

System action:

CICS continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0120I
applid Reentrant programs will not be loaded into read-only storage.
Explanation:

This is an informatory message stating that read-only programs will not be loaded into read-only storage for this execution of CICS. This is because RENTPGM=NOPROTECT was specified as a system initialization parameter.

System action:

CICS continues.

User response:

None.

You should not specify RENTPGM=NOPROTECT unless you wish to deliberately overwrite programs (to set breakpoints while testing, for example).

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0122I
applid Limit of DSA storage below 16MB is dsalimitK.
Explanation:

This message gives the limit dsalimit of the dynamic storage area (DSA) below 16MB.

System action:

CICS continues.

User response:

None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, dsalimit

DFHSM0123I
applid Limit of DSA storage above 16MB is edsalimitM.
Explanation:

This message gives the limit edsalimit of the dynamic storage area (DSA) above 16MB.

System action:

CICS continues.

User response:

None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, edsalimit

DFHSM0124
applid Transaction isolation was requested but the support is not available or storage protection is not active. Transaction isolation is not active.
Explanation:

The combination of system initialization parameters STGPROT(NO) and TRANISO(YES) is invalid. During a warm or emergency start of CICS, the catalogued system initialization parameters are incompatible with a SIT override. Although transaction isolation was requested, it is not in effect for this execution of CICS because the necessary hardware and/or operating system support is not available, and/or storage protection is not active.

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0125I
applid Transaction isolation is active.
Explanation:

Transaction isolation is requested (TRANISO=YES) and is in effect for this execution of CICS.

System action:

CICS continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0126I
applid Transaction isolation is not active.
Explanation:

Transaction isolation has not been requested (TRANISO=NO) and is not in effect for this execution of CICS.

System action:

CICS continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0. Transaction isolation can be enabled by specifying TRANISO=YES as a system initialization parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameter: applid

DFHSM0127
applid Insufficient storage to allocate requested size for DSA limit storage below 16MB (dsalimitK).
Explanation:

CICS has issued an MVS GETMAIN for the requested limit dsalimit of DSA storage below 16MB, but the GETMAIN request failed.

System action:

If the requested size is greater than the default, CICS reissues the MVS GETMAIN request using the default size for the DSALIM parameter.

If the requested size is not greater than the default, the storage manager makes an exception entry in the trace table. An error return code is sent to the domain manager DFHDMDM (the caller of the storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.

User response:

Ensure that the DSALIM system initialization parameter is specified correctly.

Ensure that the REGION parameter for the CICS job is large enough.

See the OS/390 MVS JCL Reference for further information about specifying storage on the REGION parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, dsalimit

DFHSM0128
applid Insufficient storage to allocate requested size for DSA limit storage above 16MB (dsalimitM).
Explanation:

CICS has issued an MVS GETMAIN for the requested limit dsalimit of DSA storage above 16MB, but the GETMAIN request failed.

System action:

If the requested size is greater than the default, CICS reissues the MVS GETMAIN request using the default size for the EDSALIM parameter.

If the requested size is not greater than the default, the storage manager makes an exception entry in the trace table. An error return code is sent to the domain manager DFHDMDM (the caller of the storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.

User response:

Ensure that the EDSALIM parameter is specified correctly.

Ensure that the REGION parameter for the CICS job is large enough.

See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, dsalimit

DFHSM0129
applid Insufficient storage to allocate default size for DSA limit storage below 16MB (dsalimitK).
Explanation:

Following message DFHSM0127, CICS has reduced the MVS GETMAIN request to the default size for the DSALIM system initialization parameter but the GETMAIN request has still failed.

System action:

The storage manager makes an exception entry in the trace table.

An error return code is sent to the domain manager, DFHDMDM, (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.

User response:

See DFHSM0127 for further information.

Ensure that the REGION parameter for the CICS job is large enough.

See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, dsalimit

DFHSM0130
applid Insufficient storage to allocate default size for DSA limit storage above 16MB (dsalimitM).
Explanation:

Following message DFHSM0128, CICS has reduced the MVS GETMAIN request to the default size for the EDSALIM system initialization parameter but the GETMAIN request has still failed.

System action:

The storage manager makes an exception entry in the trace table.

An error return code is sent to the domain manager, DFHDMDM, (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.

User response:

See DFHSM0128 for further information.

Ensure that the REGION parameter for the CICS job is large enough.

See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.

Destination:

Console

Modules:

DFHSMDM

XMEOUT Parameters: applid, dsalimit

DFHSM0131
applid CICS is under stress (short on storage below 16MB).
Explanation:

This message is produced when there is a shortage of storage in any of the dynamic storage areas (DSAs) below 16MB. Either the largest free area in one of the DSAs is less than the size of the internally defined cushion for that DSA, or there is at least one transaction suspended due to insufficient contiguous free storage.

System action:

An exception entry is made in the trace table to record the event.

CICS continues to operate but takes steps to alleviate the situation by, for example, slowing down the rate at which new tasks are started and by releasing storage occupied by programs which are not currently in use.

User response:

No immediate action is required. However, if the problem persists you could increase the value of the DSALIMIT parameter, if possible, or reduce the storage requirements below 16MB of your CICS system. For more information about how to do this, see the CICS Performance Guide.

Destination:

Console

Modules:

DFHSMSY

XMEOUT Parameter: applid

DFHSM0132
applid CICS is no longer short on storage below 16MB.
Explanation:

The short on storage condition reported by message DFHSM0131 has ceased.

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHSMSY

XMEOUT Parameter: applid

DFHSM0133
applid CICS is under stress (short on storage above 16MB).
Explanation:

There is a shortage of storage in one of the dynamic storage areas (DSAs) above 16MB. Either the largest free area in one of the DSAs is less than the size of the internally defined cushion for that DSA, or there is at least one transaction suspended due to insufficient contiguous free storage.

System action:

An exception entry is made in the trace table to record the event.

CICS continues to operate but takes steps to alleviate the situation by, for example, slowing down the rate at which new tasks are started and by releasing storage occupied by programs which are not currently in use.

User response:

No immediate action is required. However, if the problem persists you could, if possible, increase the value of the EDSALIMIT parameter, or reduce the storage requirements of your CICS system above 16MB. For guidance on how to do this, see the CICS Performance Guide.

Destination:

Console

Modules:

DFHSMSY

XMEOUT Parameter: applid

DFHSM0134
applid CICS is no longer short on storage above 16MB.
Explanation:

The short on storage condition reported by message DFHSM0133 has ceased.

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHSMSY

XMEOUT Parameter: applid

Start of changeDFHSM0135End of change
Start of changeapplid Insufficient storage to allocate the requested size of dsasizeK for the dsaname.End of change
Start of change
Explanation:

CICS has attempted to allocate the requested size of dsasize for the dynamic storage area dsaname but there is insufficient storage to satisfy the request.

Note:
The size of a dynamic storage area (DSA) below 16MB specified via the SIT override is rounded up to a multiple of 256KB (or 1MB for the UDSA if transaction isolation is in effect). The size of a DSA above 16MB specified via the SIT override is rounded up to a multiple of 1MB.
End of change
Start of change
System action:

An error return code is sent to the domain manager, DFHDMDM (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.

End of change
Start of change
User response:

Either reduce the value specified in the DSASZE parameter, or increase the value specified in the DSALIM parameter.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMDMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedsasize,End of changeStart of changedsanameEnd of change

Start of changeDFHSM0136IEnd of change
Start of changeapplid The size of the dsaname was specified as dsasizeK.End of change
Start of change
Explanation:

This is an informatory message giving the size dsasize of the dynamic storage area (DSA) dsaname.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMDMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changedsaname,End of changeStart of changedsasizeEnd of change

Start of changeDFHSM0137End of change
Start of changeapplid The amount of MVS storage available to CICS is low.End of change
Start of change
Explanation:

When MVS storage is requested by a JVM from Language Environment, CICS intercepts the request. This message is produced when the size of the largest contiguous unallocated block of storage above 16MB that is available for use by MVS has fallen below a system-defined threshold.

End of change
Start of change
System action:

An exception entry is made in the trace table to record the event.

CICS continues to operate but takes steps to alleviate the situation by deleting any JVMs that are currently inactive. This will have the effect of freeing any MVS storage that the inactive JVMs are holding.

End of change
Start of change
User response:

No immediate action is required. However, if the problem persists and if you are a user of Java transactions you could reduce the value of the MAXJVMTCBs parameter. This would reduce the number of JVMs which exist concurrently within CICS. For more information about how to do this, see the CICS Performance Guide.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMVNEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSM0138End of change
Start of changeapplid The amount of MVS storage available to CICS is no longer low.End of change
Start of change
Explanation:

The MVS storage shortage reported by message DFHSM0137 has ceased.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMVNEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSM0139End of change
Start of changeapplid The amount of MVS storage available to CICS is critically low.End of change
Start of change
Explanation:

This message is produced when there is no unallocated block of storage large enough to satisfy an MVS request for storage. When MVS storage is requested by a JVM from Language Environment, CICS will intercept these requests. The message means that insufficient contiguous storage was available to satisfy the MVS storage request. Either CICS has been forced to attempt to satisfy the request by releasing storage from an MVS storage cushion that it keeps in reserve or there is at least one transaction suspended due to insufficient contiguous free storage.

End of change
Start of change
System action:

An exception entry is made in the trace table to record the event.

CICS continues to operate but takes steps to alleviate the situation by deleting JVMs as the programs that own them complete and not starting new JVMs until the storage shortage is relieved.

End of change
Start of change
User response:

No immediate action is required. However, if the problem persists and if you run Java transactions you could decrease the MAXJVMTCBS parameter. For more information about how to do this, see the CICS Performance Guide.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMVNEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSM0140End of change
Start of changeapplid The amount of MVS storage available to CICS is no longer critically low.End of change
Start of change
Explanation:

The MVS storage shortage reported by message DFHSM0139 has ceased.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSMVNEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHSM0300
DFHSMUTL ERROR REPORT
Explanation:

This is the report from the local catalog storage manager domain subpool record manipulation program, DFHSMUTL. A number of lines may be written to the report:
DFHSM0300 DFHSMUTL REPORT Report header.
ADD SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY ADD SUBPOOL=xxxxxxxx has been processed successfully.
DEL SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY DEL SUBPOOL=xxxxxxxx has been processed successfully.
FOUND DFHLCD RECORD SMSUBPOL=xxxxxxxx Subpool record found by the LST command.
ERROR OPENING DFHLCD An error has occurred opening the local catalog data set. The program is terminated.
UNRECOGNISED VERB xxx IN INPUT Only ADD, DEL and LST are allowed. The statement is ignored.
UNRECOGNISED OPERAND xxxxxxxx IN INPUT Only ADD SUBPOOL=xxxxxxxx or DEL SUBPOOL=xxxxxxxx are allowed. The statement is ignored.
ERROR PROCESSING 'ADD SUBPOOL=xxxxxxxx'. R15 = X'yy'. RPL FEEDBACK CODE = X'zz'. SEE DFSMS/MVS MACRO INSTRUCTIONS FOR DATA SETS A VSAM error has occurred whilst processing an ADD SUBPOOL=xxxxxxxx command. For the meaning of the VSAM codes, refer to DFSMS/MVS Macro Instructions for Data Sets, SC26-4913. The program is terminated.
ERROR PROCESSING 'DEL SUBPOOL=xxxxxxxx'. R15 = X'yy'. RPL FEEDBACK CODE = X'zz'. SEE DFSMS/MVS MACRO INSTRUCTIONS FOR DATA SETS A VSAM error has occurred whilst processing a DEL SUBPOOL=xxxxxxxx command. For the meaning of the VSAM codes, refer to DFSMS/MVS Macro Instructions for Data Sets, SC26-4913. The program is terminated.
END OF DFHSMUTL REPORT Report trailer.

System action:

See Explanation.

User response:

If an error is reported, correct the cause and retry.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHSMUTL

[[ Contents Previous Page | Next Page Index ]]