Bringing AS400 to restricted state from batch
Michael Hudson
I am sure I have read articles about this in the past but cannot find one.
I am trying to create an weekly job that performs a SAVLIB *NONSYS (requires
the system to be in a restricted state) then re ipl's. Up to now it has run
on the console and is started manually.
I would like to make this a batch program so it can run unattended. I tried
submitting the job to QCTL but when I checked, performing an ENSBS *ALL ends
all batch jobs in QCTL.
I then tried closing all subsystems one by one in the CL and leaving QCTL
but the SAVLIB then fails as it requires the machine to be in a restricted
state.
Any ideas or pointers ?
Michael Hudson
Langley Computer Services Ltd
Bob Gilsdorf
ended, even QCTL (or QBASE in some systems). QCTL will go to an END state
from the system console. The ONLY way to have restricted state is from a
interactive job from the console (or another device hosted by QCTL). There
can be no restricted state from a batch job.
You can to run a job from the console that waits until a specific time or
event then execute the ENNNDSBS *ALL command. This job can be made to
monitor for the restricted state message in the system operator msgq before
executing a restricted state command like SAVSYS or SAVLIB *NONSYS. This job
can also restart everything afterwards by starting STRSBS QCTL
"Michael Hudson" <michael.hu...@langley.co.uk> wrote in message
news:ZYJM4.357$y8.9...@news.enterprise.net...
Tim
can sign-on and then call a program that can do what is described below.
Gernot Langle
> Can anyone help?
>
> I am sure I have read articles about this in the past but cannot find one.
>
> I am trying to create an weekly job that performs a SAVLIB *NONSYS (requires
> the system to be in a restricted state) then re ipl's. Up to now it has run
> on the console and is started manually.
>
> I would like to make this a batch program so it can run unattended. I tried
> submitting the job to QCTL but when I checked, performing an ENSBS *ALL ends
> all batch jobs in QCTL.
>
> I then tried closing all subsystems one by one in the CL and leaving QCTL
> but the SAVLIB then fails as it requires the machine to be in a restricted
> state.
>
> Any ideas or pointers ?
>
> Michael Hudson
> Langley Computer Services Ltd
AFAIK you only need to be in restricted state for a SAVSYS; you can do a SAVLIB
*NONSYS by first ending selected subsystems (e.g. ENDSBS QINTER, ENDTCP, etc.)
to remove any locks on system files and then running a SAVLIB *NONSYS in batch
subsystem (e.g. QBATCH).
--
Gernot Langle
PARAS Solutions, Inc.
http://www.parassolutions.com
mailto:gla...@parassolutions.com
Peter Brouwers
If you have the lic PGM 5769JS1 (job schedular/400) you can set the console
in a monitor function. This allows you to submit a batch job to the console.
Peter Brouwers.
"Michael Hudson" <michael.hu...@langley.co.uk> wrote in message
news:ZYJM4.357$y8.9...@news.enterprise.net...
R.E.Breedveld
Just create a break controlling program which can execute commands.
Logon to the console and put the messagequeue in break with F4, F10 and fill
in the BRKCTLPGM.
Now you can send a predefined (commandmsg) from batch to the console.
The break controlling program would catch the message and execute the
predefined command.
Success,
René E. Breedveld
Mid Range Systems Consultancy B.V.
"Michael Hudson" <michael.hu...@langley.co.uk> schreef in bericht
Glenn Holmen
You are right that SAVLIB *NONSYS needs a restricted state, however
SAVLIB *IBM and SAVLIB *ALLUSR don't.
Between them they save everything a *NONSYS does.
It's a good idea to end any subsystems not required for the backup but it
not essential.
I use this method for a nightly backup.
You need to end host servers before running the SAVLIB *IBM though,
otherwise some objects in lib QIWS won't get saved.
Regards,
Glenn.
Michael Hudson wrote in message ...
Lptoro
exactly that (and a lot more) that I used in my last job. It worked very well.
It would automaticly run my *NONSYS at a prescribed time, apply PTFs
(optional) that I had loaded onto the CD-ROM, and even RCLSTG, if needed,
before re-IPLing.
Good Luck,
Paul
Thomas
I have to ask... why do you need a weekly SAVLIB *NONSYS? Are you
adding, removing, updating your IBM products weekly? Why include the
SAVLIB *IBM portion at all on a weekly basis? Remove that and
thereby remove the need for restricted state. Just do the SAVLIB *ALLUSR
weekly; and only do the SAVLIB *IBM when needed, such as after a release
upgrade or after a cume package.
But if you have reasons, I'm curious to hear them. I suspect some sites
have reasons; I've just never heard them.
Tom Liotta
In article <ZYJM4.357$y8.9...@news.enterprise.net>,
"Michael Hudson" <michael.hu...@langley.co.uk> wrote:
> Can anyone help?
>
> I am sure I have read articles about this in the past but cannot find
one.
>
> I am trying to create an weekly job that performs a SAVLIB *NONSYS
(requires
> the system to be in a restricted state) then re ipl's. Up to now it
has run
> on the console and is started manually.
>
> I would like to make this a batch program so it can run unattended. I
tried
> submitting the job to QCTL but when I checked, performing an ENSBS
*ALL ends
> all batch jobs in QCTL.
>
> I then tried closing all subsystems one by one in the CL and leaving
QCTL
> but the SAVLIB then fails as it requires the machine to be in a
restricted
> state.
>
> Any ideas or pointers ?
>
> Michael Hudson
> Langley Computer Services Ltd
>
>
--
Tom Liotta
AS/400 systems programmer
Sent via Deja.com http://www.deja.com/
Before you buy.
Michael Hudson
it's done" and I have been tasked with automating it. You raise a very good
point though and it is worth investigating. If I can automate it easily I
think I'll do that first then tackle the question.
Michael
Thomas <tho...@inorbit.com> wrote in message
news:8e5ejj$evn$1...@nnrp1.deja.com...
Michael Hudson
Thank You
Michael Hudson
Michael Hudson <michael.hu...@langley.co.uk> wrote in message
news:ZYJM4.357$y8.9...@news.enterprise.net...