DFS686W IMS jobname imsid INIT/TERM (nn) FAILURE RC=xxxxyyzz
Explanation
An SVC initialization or termination failure occurred
during processing. The jobname and imsid identify
the IMS system. If the imsid field
is
N/A, the imsid was unavailable
at the time the message was issued. The function code nn identifies
the SVC initialization or termination function processing at the time
of the error. Possible function code values are: - Code
- Function
- 01
- INITSVC, SVC initialization
- 02
- INITDEP, dependent region initialization
- 03
- Reserved
- 04
- TERMSVC, SVC termination
- 05
- TERMDEP, dependent region termination
- 06
- Reserved
- 07
- INITSCD, initialize SCD in IMS SVC vector table
- 08
- KILLSVC, clear SVC directory entries
- 09
- INITBAT, batch region initialization
Return code xxxxyyzz identifies
the type of failure and where it occurred:
- xxxx
- If nonzero, xxxx is the return code from a service called by the SVC. For IMODULE and IMSAUTH failures, see the IMS system services return code information.
- yy
- The module that issued the message:
- 03=DFSVC200
- 05=DFSVCI00
- zz
- The return code from the SVC module that indicates what type of failure occurred.
The values for yyzz for DFSVC200
failures are:
- 301
- GETMAIN failed for DFSVCI00 parameter list.
- 302
- Invalid function
- 303
- SVC directory block address is zero or unable to locate directory entry for region.
- 304
- Region type of caller is invalid for request.
- 305
- Vector table address is zero.
- 306
- SVC release is incompatible with IMS release.
- 307
- SVC number is invalid in SSCD/SCD.
- 308
- GETMAIN failed for DCB work area.
- 309
- SSCD copy failed.
- 30A
- SVC number changed in SSCD after SVC validation.
- 30B
- SCD address is zero.
- 30C
- RMPL address is zero.
- 30D
- Non-authorized caller of an authorized function.
- 30E
- Invalid SCDRGTYP value.
- 30F
- Online IMS caller is not in a system key.
The values for yyzz for DFSVCI00
failures are:
- 501
- Invalid function
- 502
- Invalid caller
- 503
- Duplicate IMSID
- 505
- GETMAIN failed for SVC directory block.
- 506
- GETMAIN failed for SVC vector table.
- 507
- IMSAUTH BLDSSCT failed.
- 508
- IMODULE LOAD for DLS/LSO table failed.
- 509
- IMODULE LOAD for an IMS SVC routine failed.
For batch IMS, the routine is one of the following: DFSAOS70, DFSV4200, DFSV4300, or DFSV4400.
Ensure that these modules are in an authorized library.
For online IMS, the routine is one of the following: DFSAOS70, DFSASK00, DFSBCK00, DFSICSC0, DFSUICC0, DFSV4100, DFSV4200, DFSV4300, DFSV4400, or DFSVES00.
Ensure that these modules are in the IMS SDFSRESL data set.
- 50A
- IMODULE LOAD for DFSAOSF0 failed. For batch IMS, ensure that this module is in an authorized library.
- 50B
- IMODULE LOAD for DFSISI00 failed.
- 50C
- GETMAIN failed for SSVT.
- 50D
- Caller is using invalid SVC number.
- 50E
- IMODULE GETMAIN for key 7 SCD failed.
- 50F
- IMSAUTH SSCTSCD failed.
- 510
- IMODULE LOAD for DFSSTM00 failed. For batch IMS, ensure that this module is in an authorized library.
- 511
- IMODULE LOAD for DFSKPXT0 failed. For batch IMS, ensure that this module is in an authorized library.
- 512
- IMODULE LOAD for DFSTOPR0 failed. For batch IMS, ensure that this module is in an authorized library.
- 513
- IMODULE GETMAIN for CBT header failed.
- 514
- IMODULE LOAD for DFSBC000 failed. For batch IMS, ensure that this module is in an authorized library.
- 515
- Unable to initialize DFSCBT10 blocks. For batch IMS, ensure that this module is in an authorized library.
- 516
- Unable to initialize CBTE blocks.
- 517
- IMODULE LOAD for DFSSPF00 failed. For batch IMS, ensure that this module is in an authorized library.
- 518
- IMODULE LOAD for DFSLMGR0 failed. For batch IMS, ensure that this module is in an authorized library.
- 519
- GETMAIN failed for DFSSTM00 work area.
- 51A
- Unable to obtain SRBC IPAGE.
- 51B
- Invalid SSCD eyecatcher in caller-passed SSCD block.
- 51C
- IMODULE LOAD for DFSLRH00 failed. For batch IMS, ensure this module is in an authorized library.
- 51D
- Module assembled at level incompatible with IMS release.
- 51E
- Batch Region initialization failed - two IMS images in the same address space using the same IMS ID.
- 51F
- Batch Region initialization failed - two IMS images in the same TSO address space.
- 520
- Batch Region initialization failed - two IMS images in the same address space using the same TCB.
- 521
- Dependent Region initialization failed - two IMS images in the same address space, same IMS ID, and one of the images not a dependent region.
- 522
- Dependent Region initialization failed - two IMS images in the same address space, same IMS ID, both dependent regions, but different TCBs. (This is not a dependent region waiting for a control region to come up and going through SVC INIT retry logic.)
- 523
- Dependent Region initialization failed - two IMS images in the same address space and one of them is a control region.
- 524
- Dependent Region initialization failed - two IMS images in the same TSO address space.
- 525
- Dependent Region initialization failed - two IMS images in the same non-TSO address space, not control regions, but the same TCB.
- 526
- IMODULE LOAD for DFSDCFR0 failed. For batch IMS, ensure that this module is in an authorized library.
- 527
- IMODULE LOAD for DFSDXES0 failed. For batch IMS, ensure that this module is in an authorized library.
- 528
- IMODULE LOAD for DFSDMAW0 failed. For batch IMS, ensure that this module is in an authorized library.
- 529
- IMODULE GETMAIN for key 7 CFB failed.
- 52A
- IMODULE LOAD for DFSDCFC0 failed. For batch IMS, ensure that this module is in an authorized library.
- 52B
- IMODULE LOAD for DFSRRSB0 failed. For batch IMS, ensure that this module is in an authorized library.
- 52C
- Unable to load module DFSRTMI0. For batch IMS, ensure that this module is in an authorized library.
- 52D
- Unable to establish resource cleanup environment for IMS.
- 530
- Initialization of IMODULE services failed. See the preceding DFS4342E message for details about the failure. xxxx in the message is the return code from IMODULE services initialization module DFSMODX0.
- 532
- Double INITBAT call. DFSVCI00 was called for batch SVC initialization, but batch initialization was already done.
- 533
- DFSVCI00 was called for batch SVC initialization, but the region type did not indicate it was a batch IMS region.
- 534
- IMODULE LOAD for DFSMDA00 failed. For batch IMS, ensure that this module is in an authorized library.
- 535
- Getmain failed for BLDL in directed load subroutine.
- 536
- BLDL failed to locate the requested module in directed load subroutine.
- 537
- STORAGE OBTAIN for module directed load failed.
- 538
- LOAD failed to load module into storage.
- 539
- PGSER PROTECT module DFSISI00 failed.
System action
SVC initialization or termination processing terminates. The SVC module passes a return code to the caller, who might issue an IMS abend.
Programmer response
Determine the cause of the failure and correct the problem. For IMS batch job DFSVCI00 errors
that involve IMODULE LOAD, the modules that are being loaded must come from an APF-authorized
library. If you are using a DFSRESLB DD statement in your batch job, ensure that the modules that
are listed under Specifying the DFSRESLB DD statement in IMS batch procedures
in The specification of IMS procedures are all included in DFSRESLB, and that all of the
data sets in the DFSRESLB DD concatenation are APF-authorized.