We have all of our coding on the 192 disk. The only thing VTAM does is
run the VTAMPROF GCS from the 192 disk. The same is true for almost any
other service machine (GCS, RSCS, OPERATOR, SFS). They all link the same
minidisk as 192, obviously RO, and run customized EXEC or GCS.
Afterwards we let
ty, Berry, do you need to be a SECUSER to issue the SEND VTAM command?
Berry van Sleeuwen berry.vansleeu...@xs4all.nl
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
11/09/2010 11:25 AM
Please respond to
IBMVM IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re:
As opposed to CMS, the PROFILE GCS doesn't need to be on the A-disk. Any
disk accessed at IPL is good.
- in the good old days, GCS accessed 595 S; 59E Y/S; 191 A; and 191 A
- now only 191 A and 192 are left.
In these good old days, I stored all customzed execs (including the common
PROFILE GCS)
I didn't now this. So we even do not need the PROFILE GCS on the 191
disk and store the PROFILE GCS on the 192 disk. Or perhaps even only
link the RO disk as 191 instead of keeping the local 191 minidisk. Nice.
Op 09-11-10 18:34, Kris Buelens schreef:
As opposed to CMS, the PROFILE GCS doesn't
We have class c on our own users and/or use user OPERATOR (who is
secuser) to send the commands. Since our profiles and such are
maintained and distributed automatically by a sevicemachine, usually
OPERATOR is used to issue the commands. And also because we can have
PROP control the authorisation
I will be out of the office starting 11/09/2010 and will not return until
11/16/2010.
I will be out of the office on nov 10th and returning nov 16th. If your
matter is urgent, please contact Terri Green at 877-700-0184.
'PIPE CP Q ALLOC ALL' ,
'| TAKE LAST 1' ,
'| CONSOLE' ,
'| SPECS W6 1' ,
'| VAR sysres' ,
'| CP QUERY CPOWNED' ,
'| PICK W2 == /'sysres'/' ,
'| SPECS W2-* 1' ,
'| CONSOLE'
This won't work. You cannot set the REXX variable and use it in the same
pipe.
'PIPE CP Q ALLOC
