Posted: Thu Oct 30, 2003 1:52 pm Post subject: DFS3620 while restarting the region
Hi! Some more questions...
At present I am starting subsystem DSN (DB2) when IMS is already up, with
/START SUBSYS SSM xdb2
I get no error message: everything goes fine.
If I close the MPR region:
/STOP REGION something
and then I restart it:
/START REGION IVP51M41
I get:
Code:
DFS058I 19:18:29 START COMMAND IN POGRESS
DFS3620I REQUIRED RESOURCE UNAVAILABLE - RC = 0028 - FC = 0504 - RESOURCE ID =
IMOD-LD - SUBSYS NAME= DSN - JOBNAME = IVP51M41
DFS551I MESSAGE REGION IVP51M41 STARTED ID=00002 TIME=1918 CLASS=001,000,000,000
Then a /DISPLAY SUBSYS ALL shows that DSN is connected, so it is not necessary to /START it again.
Why do I get DFS3620I ? It might be related to the abend I am getting when I try and use SQL (see my other posts...).
Here is the manual:
[code:1:222ea4b584]DFS3620I REQUIRED RESOURCE UNAVAILABLE - RC=uu - FC=vv RESOURCE
ID=xxxxxxxx - SUBSYS NAME = yyyy - JOBNAME = zzzzzzzz.
Explanation: The IMS system encountered a resource constraint while processing a request to connect to an external subsystem.
The following values for the return code (RC-uu), function code (FC-vv), resource ID-xxxxxxxx, subsys name-yyyy and jobname-zzzzzzzz are defined:
uu The return code is passed back to the caller. Refer to the table in Appendix B, "Return Codes and Function Codes" in topic B.0 of this manual.
*************** 28
vv The function code indicates the module name that encountered the problem. Refer to the function code table in Appendix B, "Return Codes and Function Codes" in topic B.0 to find the module name equated to the FC number given.
*************** 0504
xx..xx The resource ID indicates that a resource was required but could not be obtained or was nonexistent. The possible values are:
*************** IMOD-LD
zzzzzzzz Indicates the region where the connection failed. The PROCLIB member specified via the SSM parm for this region contains a subsystem definition which is not contained in the control region member.
*************** IVP51M41
Hi Kolusu, thanks for your reply!
No, my subsystem name is really DSN: XDB2 is part of the subsystem member (SSM) name IVP4XDB2 of PROCLIB, where DSN is well specified as the subsystem name.
Have you by chance taken a look at my other questions in the former posts? Only if you have two minutes, of course.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum