The CMGCMD ALLOW parm tells where the command could execute.
Therefore, if you had done a CHGCMD PWRDWNSYS ALLOW(*INTERACT) you would not
be able to issue the PWRDWNSYS command except interactively. You could not
execute it in batch, or inside any CL program.
The Parm CONFIRM *INTERACT gives a "pop-up" screen when you run it
interactively so the operator can confirm, but if they run it in batch, it
just executes as it now for you.
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, September 21, 2007 8:03 AM
To: Midrange Systems Technical Discussion
Subject: Re: operators and PWRDWNSYS
I have a question about PWRDWNSYS CONFIRM(*INTERACT).
Does CONFIRM(*INTERACT) match CHGCMD ALLOW(*INTERACT)
or does it match ALLOW(*INTERACT *IPGM)?
I have a program that does a save and a bunch of stuff, then does an IPL.
I would like to change the environment variable associated with CONFIRM to
be *INTERACT but I do not want it to hold up that program (since the IPL
often occurs "lights out").
Worse comes to worse, I do have a 270 I could test this on.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.