Re: Updating PROFILE GCS Nondisruptively

2010-11-09 Thread Berry van Sleeuwen
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 the machine reaccess that disk to get the new content
available.

In case of VTAM:

Update file.
SEND VTAM ACCESS 192 D

Regards, Berry.

Op 08-11-10 23:49, George Henke/NYLIC schreef:

 What is the best way to update PROFILE GCS without corrupting VTAM?

 VTAM has R/W access to it and yet I must update GCS through an LU?

 Will I not bring down VTAM or corrupt VTAM's 191 if I update it while
 VTAM is up?.






Re: Updating PROFILE GCS Nondisruptively

2010-11-09 Thread George Henke/NYLIC
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: Updating PROFILE GCS Nondisruptively






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 the machine reaccess that disk to get the new content
available.

In case of VTAM:

Update file.
SEND VTAM ACCESS 192 D

Regards, Berry.

Op 08-11-10 23:49, George Henke/NYLIC schreef:

 What is the best way to update PROFILE GCS without corrupting VTAM?

 VTAM has R/W access to it and yet I must update GCS through an LU?

 Will I not bring down VTAM or corrupt VTAM's 191 if I update it while
 VTAM is up?.







Re: Updating PROFILE GCS Nondisruptively

2010-11-09 Thread Kris Buelens
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) on MAINT 59E, linked by all GCS users.  Whne GCS no longer had
an S- nor Y-disk, I simply made our GCS users LINK MAINT 59E 192 and the
common PROFILE GCS still worked. GCS, AVSVM, and some less common ones,
didn't even have a 191 A-disk.

2010/11/9 Berry van Sleeuwen berry.vansleeu...@xs4all.nl

 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 the machine reaccess that disk to get the new content
 available.

 In case of VTAM:

 Update file.
 SEND VTAM ACCESS 192 D

 Regards, Berry.

 Op 08-11-10 23:49, George Henke/NYLIC schreef:
 
  What is the best way to update PROFILE GCS without corrupting VTAM?
 
  VTAM has R/W access to it and yet I must update GCS through an LU?
 
  Will I not bring down VTAM or corrupt VTAM's 191 if I update it while
  VTAM is up?.
 
 
 
 




-- 
Kris Buelens,
IBM Belgium, VM customer support


Re: Updating PROFILE GCS Nondisruptively

2010-11-09 Thread Berry van Sleeuwen
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 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) on MAINT 59E, linked by all GCS users.  Whne GCS
 no longer had an S- nor Y-disk, I simply made our GCS users LINK MAINT
 59E 192 and the common PROFILE GCS still worked. GCS, AVSVM, and some
 less common ones, didn't even have a 191 A-disk.

 2010/11/9 Berry van Sleeuwen berry.vansleeu...@xs4all.nl
 mailto:berry.vansleeu...@xs4all.nl

 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 the machine reaccess that disk to get the new
 content
 available.

 In case of VTAM:

 Update file.
 SEND VTAM ACCESS 192 D

 Regards, Berry.

 Op 08-11-10 23:49, George Henke/NYLIC schreef:
 
  What is the best way to update PROFILE GCS without corrupting VTAM?
 
  VTAM has R/W access to it and yet I must update GCS through an LU?
 
  Will I not bring down VTAM or corrupt VTAM's 191 if I update it
 while
  VTAM is up?.
 
 
 
 




 -- 
 Kris Buelens,
 IBM Belgium, VM customer support


Re: Updating PROFILE GCS Nondisruptively

2010-11-09 Thread Berry van Sleeuwen
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 as well as storing the commands and
output into the operator log.

Regards, Berry.

Op 09-11-10 17:27, George Henke/NYLIC schreef:

 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: Updating PROFILE GCS Nondisruptively



   





 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 the machine reaccess that disk to get the new content
 available.

 In case of VTAM:

 Update file.
 SEND VTAM ACCESS 192 D

 Regards, Berry.

 Op 08-11-10 23:49, George Henke/NYLIC schreef:
 
  What is the best way to update PROFILE GCS without corrupting VTAM?
 
  VTAM has R/W access to it and yet I must update GCS through an LU?
 
  Will I not bring down VTAM or corrupt VTAM's 191 if I update it while
  VTAM is up?.
 
 
 
 



Don India - Out of Office

2010-11-09 Thread Donald India
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.


Re: How to determine SYSRES

2010-11-09 Thread Alan Ackerman
'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 ALL' ,
   '| TAKE LAST 1' ,
   '| CONSOLE' ,
   '| SPECS W6 1' ,
   '| VAR sysres' 

'PIPE CP QUERY CPOWNED' ,
   '| PICK W2 == /'sysres'/' ,
   '| SPECS W2-* 1' ,
   '| CONSOLE' 

Not tested. But then the first pipe wasn't tested either.

Alan Ackerman