In
<8464779473941406.wa.elardus.engelbrechtsita.co...@listserv.ua.edu>,
on 01/25/2013
at 07:07 AM, Elardus Engelbrecht <elardus.engelbre...@sita.co.za>
said:
>Perhaps irrelevant and more irrelevant these days, but why was IBM
>distributing the proc DEALLOC (renamed by some sites to X) in the
>first place?
The hope that nobody would add a new proc with the same name. START X
has unforseen consequences if someone adds a proc called X.
>If the proc does not exist (ie no member found) in those days, are
>the allocation/de-allocation processes still driven or not?
Back in OS/360 a JCL error message was written to a system message
block (SMB) and there were no data for SYSOUT writers until an SMB/DSB
chain was added to the output queue, which was done by the Scheduler.
Se even with a JCL error there was some Initiator code run.
[1] Back in OS/360 it needed to
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2 <http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
