Jay Maynard wrote:
[...]
> How do you explain to an
operator that some things can and should be ended via CANCEL, while others
need STOP and using CANCEL on them is a bad thing, while still others will
just plain reject a CANCEL?
I do that that way:
Well, there are plenty of tasks, we call them started tasks.
We list them using D A,L command, don't ask about full syntax.
The tasks are stopped in different very individual manner, for example:
P TCPIP closes TCPIP
P FFST also closes FFST, but requires confirmation.
VTAM is closed via Z NET,
APPC is closed via CANCEL
CICS is closed via F CICSRGN,CEMT P SHUT
DB2 is closed via -DSN STOP DB2,
LLA should be closed before VLF...
no, no, !
You *don't* have to note it or remember it!
Everything is in our *procedures*.
Yes, we have tons of procedures, we wrote them for you.
Is it acceptable explanation ?
<g>
BTW: I really *like* this black magic: I stop several tasks using
different commands, I look like a guru... <vbg>
That's what I explain on introductory courses: you need a lot of
knowlegde to work with this system, even simple dataset allocation can
be very complicated and can require a lot of knowledge. Compare it to
other systems, there you don't so much knowledge, and you don't need to
allocate files at all.
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
