Re: 36EE Files Library Determination

On 13-Sep-2011 11:45 , Jerry C. Adams wrote:

Hadn't thought about that, Doug. Only works in a CL, of course, if
there isn't a higher level OCL procedure. But if that's the case, I
could plug it in the higher OCL. I've gotten bit on the rump before
with an OCL calling a CL that then tried to run the STRS36PRC
command.

Douglas Handy on Tuesday, September 13, 2011 12:41 PM wrote:

If nothing else, you could call STRS36PRC and call a procedure
which contained something like:

// LOCAL OFFSET-?1'501'?,BLANK-10,DATA-'?FLIB?'

then read it back out of the *LDA when you are done. You could
pass in the starting LDA position, which defaults to 501 above.
Not as nice as an API, but gets the job done without assumptions.

Perhaps the following would work? I can not test, though I seem to recall doing something similar in the past; at least using the failed Start S36 Procedure as an indication of already running, althoug not the attempt to pass the procedure invocation to the S36EE as recovery.

Make that same procedure or similar, e.g. name SETLDAFLIB in QS36PRC, but always invoked as the following CLP:

pgm /* SETLDAFLIB */
strs36prc SETLDAFLIB
monmsg (xxx#### /* monitor OCL already active */) exec(do)
rcvmsg ... rmv(*yes) msgtype(*excp)
call qcapcmd ( 'SETLDAFLIB' +
... /* Type of command processing=2 */ )
enddo
return
endpgm

Regards, Chuck