ca.portal.admin

Re:Assembler question

Discussion created by ca.portal.admin on Jun 1, 2009
We have a WTOREXIT routine that works fine when linked with the IDMS
startup module. But when I try to run it the new recommended way ( EXEC
PGM=3DRHDCOMVS,PARM=3D('WTOR=3DWTOREXIT') ), it disables itself at =
startup.

I have tracked the problem to the code below. But my assembler skills
are nowhere near the level of the person who wrote this 28 years ago.
Can someone explain to me what this code does? Any theories as to why
it fails when executed the new way would be welcome also.


STINIT DS 0H SUBTASK INIT ROUTINE
* ESTABLISH OPERATOR COMMUNICATIONS AND REMOVE START MSG
EXTRACT MF=3D(E,EXTPRM) GET TIOT AND COMM FIELD POINTERS
L R1,TIOTPNT LOAD THE TIOT POINTER ADDRESS
MVC JOBNAME,0(R1) MOVE THE JOB NAME TO THE WTOR
* IDENTIFY AND ATTACH THE SUBTASK ROUTINE
IDENTIFY EPLOC=3DWAITNAM,ENTRY=3D&WAIT IDENTIFY MESSAGE WAIT RTN
LTR R15,R15 ANY ERRORS FOUND?
BNZ ERROR YES, DISABLE THE WTOR EXIT
ATTACH SF=3D(E,ATTACH) ATTACH THE MESSAGE WAIT ROUTINE
LTR R15,R15 ANY ERRORS FOUND?
BNZ ERROR YES, DISABLE THE WTOR EXIT
OI STATUS,INIT SET THE INIT DONE FLAG
BR LINK RETURN TO THE CALLER

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Assembler question
"Kay, the parm WTOR=WTOREXIT does not currently work if the WTOREXIT has
an IDENTIFY statement in the assembler code. The IDENTIFY will return a
code of x'0000000C' and the WTOREXIT will not be established. TRhe
reason is that it cannot find a CDE for the WTOREXIT module. That is an
IBM control block established when loaded thru IBM LOAD from a STEPLIB.
The reason we fail on the IDENTIFY is that CA-IDMS LOADs the WTOREXIT
module from the CDMSLIB - therefore - no CDE for the IDENTIFY.
This is fixed in release 18.0 but in the meantime you would have to link
the WTOREXIT into either the RHDCOMVS module in your STEPLIB or create
the old style startup module.
**
NOW WHAT!!
Kay, Please open an issue and have them refer that issue to me (Ed
McKinney) and I will write an APAR to fix this problem. This will
require that the WTOREXIT reside in a STEPLIB loadlib when using the
WTOR= startup PARM.
Regards,
Ed McKinney (CA support)

Outcomes