CA Deliver - RMOSTC Task Abend With RMODBI01 Message and Code U0041
Article ID: 195858
Updated On:
Products
OM Deliver
OM View
Issue/Introduction
The client received an abend in their CA Deliver RMOSTC task, with "RMODBI01 ... Error=1708 ... Dnnn" and U0041 messages.
Environment
Release : 14.0
Component : CA Deliver
Resolution
A dump of the first Deliver database extent showed that the database had 2 data extents in use (....D0000001 and ....D0000002).
There being no client evidence of the existence of D0000002 indicates that:
. The .D0000002 extent was manually deleted.
. The .D0000002 extent is not in the catalog.
A job to run, to produce a .D0000002 data set, which would enable Deliver jobs to be run (including bringing up the RMOSTC task), would be the below, but it should be noted that whatever data was in that extent would be lost:
//XXXXXXXX JOB ...
//RMODBASE EXEC PGM=RMODBASE,PARM='DLVR.DB2' <=== TEMPORARY DB NAME
//STEPLIB DD DISP=SHR,DSN=DLVR.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ADDDS UNIT=3390 CYLINDER=10 BLKSIZE=3768 VOLSER=XXXXXX
ADDDS UNIT=3390 CYLINDER=10 BLKSIZE=3768 VOLSER=XXXXXX
/*
//
Then, use =3.4, to rename the DLVR.DB2.RMODBASE.D0000002 to DLVR.DB1.RMODBASE.D0000002.
Note: The above procedure would be the same in there was a missing .D000000n extent.
-----------------------------------------------------------------------------------------
After performing the above, the client was then able to start their RMOSTC task successfully.
To again note, the addition of the above is to an empty data set to take the place of the data set that is currently not there, but it will enable you to move on.
There being no client evidence of the existence of D0000002 indicates that:
. The .D0000002 extent was manually deleted.
. The .D0000002 extent is not in the catalog.
A job to run, to produce a .D0000002 data set, which would enable Deliver jobs to be run (including bringing up the RMOSTC task), would be the below, but it should be noted that whatever data was in that extent would be lost:
//XXXXXXXX JOB ...
//RMODBASE EXEC PGM=RMODBASE,PARM='DLVR.DB2' <=== TEMPORARY DB NAME
//STEPLIB DD DISP=SHR,DSN=DLVR.CVDELOAD <=== Modify, if used
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ADDDS UNIT=3390 CYLINDER=10 BLKSIZE=3768 VOLSER=XXXXXX
ADDDS UNIT=3390 CYLINDER=10 BLKSIZE=3768 VOLSER=XXXXXX
/*
//
Then, use =3.4, to rename the DLVR.DB2.RMODBASE.D0000002 to DLVR.DB1.RMODBASE.D0000002.
Note: The above procedure would be the same in there was a missing .D000000n extent.
-----------------------------------------------------------------------------------------
After performing the above, the client was then able to start their RMOSTC task successfully.
To again note, the addition of the above is to an empty data set to take the place of the data set that is currently not there, but it will enable you to move on.
Feedback
Yes
No
Powered by
