Re: SNDRCVF in a CL program

I'm pretty sure the practical uses for acquiring devices were from way back in IBM System 3 Model 15D days, when the computer could only run one program at a time, or two if you were using CCP (Communications Control Program).  I think the example back then was something like airline reservations, where a single program would acquire all the reservation agents terminals and handle reservation requests. These days we don't have the same constraints, but thanks to IBM's backwards compatibility, we could still run a program like that :)


On 9/29/2021 10:40 AM, James H. H. Lampert via MIDRANGE-L wrote:

Not sure why this initially went off-List.

On 9/29/21 10:21 AM, Larry "DrFranken" Bolhuis wrote:

Maybe I'm crazy but I would try it and find out which CPF message I got. :-)

As a matter of fact, a few minutes after I broadcast my question, I hit on a simple way to do exactly that: I made a copy of the CL program in question (it's a front-end for doing a QShell "rm -r"; I call it DELTREE, and the display file consists entirely of a confirmation screen for the specified path), ripping out the QShell call, and tried it in a batch job.

It crashed with a CPF4103, "Device *REQUESTER not found while opening file DELTREE in library MERCURY."

And no, Larry, you're not crazy, and neither am I. Maybe the author of the CL manual and/or the helptext was a bit nuts, for having not documenting what Mr. Dow pointed out about having to direct it to a device.

(A couple of decades ago, I found out about acquiring devices, and wrote a test program to do just that; I don't think I ever did find a practical use for it.)

--
JHHL