×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have analysed the logs and found that the subsystem QSYSWRK could not be killed prior to the start of backup.There was a job QSYSWRK running in the susbsytem QSYSWRK which could not be killed due to which the QSYSWRK sbs could not be ended.
This prevented the system from entering the restricted state.The system logs suggest the follwong:
Message . . . . : *SAVSYS bypassed for control group SAVALL.
Cause . . . . . : The save system (*SAVSYS) was bypassed for control group
SAVALL because restricted state could not be reached. The end of all
subsystems would not bring the system down due to activity in progress on
the system. Processing will continue within the control group.
Since the system could not come to restricted state ,it could not pop up after the backup was over.Please can you or anyone suggest how we can prevent this from happening again.
Also is my analysis correct on system not coming up after backup.
Please advice asap.
Will it be worthwhile to schedule a job which would end the QSYSWRK subsystem 5 minutes prior to start of backup.
I am also attaching the details of the control group SAVALL thru which the daily backup runs.:
Regards
Sneha
--- On Fri, 16/4/10, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
From: rob@xxxxxxxxx <rob@xxxxxxxxx>
Subject: Re: Server Hung
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Friday, 16 April, 2010, 12:25 PM
I assume that this is a BRMS version of GO SAVE 21, right? Otherwise, why
would you need restricted state?
Anyway, can you find the joblog that brings it out of restricted state and
see if there's any abnormality?
Just as a matter of habit whenever I go into restricted state I always IPL
to get out of it. However I believe that a STRSBS SBS(see value of system
value QCTLSBSD) should also work to get your system out of restricted
state. If you have an HMC you should also have a console on there,
(unless, for some silly reason you still use twinax as a console). That
device should have been able to do a STRSBS.
Sample: On a system with QCTLSBSD set to QCTL you do an ENDSBS *ALL
*CNTRLD DELAY(120). After the two minutes (and change) your system is in
restricted state. You do a WRKACTJOB and you will see QCTL with a status
of END and your system console job will be in there. END basically means
that no new job (other than the system console job) will start. Now, you
do a STRSBS QCTL and it brings it out of END state and runs any autostart
job entries associated with that subsystem. One of these will be the job
QSTRUPJD. This utilizes system value QSTRUPPGM to start your system up.
Find that joblog.
Rob Berendt
Display Backup Control Group Entries
Group . . . . . . . . . . : SAVAULL
Default activity . . . . : FFFFFFF
Text . . . . . . . . . . : Entire System Backup no IPL
Auxiliary Weekly Retain Save
Backup List Storage Activity Object While
Seq Items Type Pool Device SMTWTFS Detail Active
10 *EXIT *DFTACT
20 *SAVSYS *DFTACT
30 *IBM *DFTACT *NO *NO
40 *ALLUSR *SYSBAS *DFTACT *ERR *NO
50 *ALLDLO *DFTACT *NO *NO
60 *LINK *ALLAVL *DFTACT *YES *NO
70 *EXIT *DFTACT
80 *EXIT *DFTACT
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.
midrange.com
