|
Hi, Larry,
Using RTVCLSRC of QMNSAVE will always be "up to date" and it should be easy enough to issue RTVCLSRC of QMNSAVE after any PTFs or OS upgrades (saving to a new member name), to see what was changed ... use CMPPFM for that.
So, it should be fairly easy to maintain a "customized" version of e.g. QMNSAVE, especially if kept in a separate QSYS1 library, where IBM PTFs will not directly affect it.
Hope that helps,
Mark S. Waterbury
On Sunday, March 17, 2019, 4:44:11 PM EDT, DrFranken <midrange@xxxxxxxxxxxx> wrote:
Thousand pardons that I was not more specific, it seemed rather obvious
my my chair!!
My RFE will be to add an option to leave the system in restricted state
after the backup. Very simple it seems and a default of No to that would
be appropriate and leave the options to work as they do now by default.
Yes you could write your own and I have many times. Thing is when IBM
enhances those saves you then have to enhance yours. And if you read
what's behind F1 it's not complete and has not been for several releases.
Go BACKUP? People still use that. YIKES!
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 3/17/2019 1:45 PM, Mark Waterbury wrote:
Hi, Larry,
Okay, but an "RFE" to alter what, exactly, -- the behavior of "GO SAVE" options 21, 22 and 23? Perhaps add another option to the list of options when you select option 20, to ask if you want to leave the system in "restricted state"?
If you type GO SAVE and press Enter, then put the cursor on top of the 21, 22 or 23 in the menu and press F1=Help, then page down to the bottom, it documents the CL commands that will be run, you you could always just write your own CL program to do the "save" the way you want.
And, also, what about "GO BACKUP"?
Perhaps a more generic approach would be an RFE to request IBM to provide source code for those system menus (SAVE, BACKUP, etc.) and the programs that run for those menu options, so they could be "customized" if needed for a given customer site...?
See also:
https://www-01.ibm.com/support/docview.wss?uid=nas8N1017315
That document describes how to modify the CL programs invoked by the GO SAVE menu options 21, 22, and 23 ...
NOTE: I suggest compiling any new version into a new library, e.g. QSYS1, and then, when you want that behavior, you can issue e.g.: CHGSYSLIBL QSYS1 *ADD to add QSYS1 ahead of QSYS in the system portion of the library list, or if you always want to use the modifications, issue: CHGSYSLIBL QSYSLIBL ... This works because the GO SAVE menu issues an unqualified CALL to those programs for those menu options.
Some related information: https://www-01.ibm.com/support/docview.wss?crawler=1&uid=nas8N1011650
Hope that helps ... how do others handle this situation?
Mark S. Waterbury
On Sunday, March 17, 2019, 12:51:52 PM EDT, DrFranken <midrange@xxxxxxxxxxxx> wrote:
CHGIPLA STRRSTD(*YES) has no effect after a save.
During an IPL the system notes this setting and does not start the
controlling subsystem if set to *YES. It also resets it to *NO at this
point.
At the end of backup options 21, 22, and 23 on the SAVE menu, the system
starts the controlling subsystem.
I think an RFE is in order.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 3/16/2019 11:39 PM, Mark Waterbury wrote:
I think you're right -- I think the GO SAVE 21 just takes the system to restricted state, does the back-up, then returns to "normal"...
On Saturday, March 16, 2019, 10:32:40 PM EDT, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:
I know there's that, but I recall it only was applicable to something like PwrdwnSys Restart(*yes).
The 21/Save is not really what I consider an IPL.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Mark Waterbury
Sent: Saturday, March 16, 2019 7:20 PM
To: Midrange Systems Technical Discussion
Subject: Re: Full save then restricted state?
CHGIPLA
On Saturday, March 16, 2019, 10:02:51 PM EDT, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:
I've been out of the sysadmin world for some time but isn't there an option to change the defaults and not start QCTL (or whatever SBS you have configured) after the backup? Or, maybe it prompted?
I seem to recall doing that.
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Saturday, March 16, 2019 2:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: Full save then restricted state?
Can you say: "Fraught with peril?"
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 3/16/2019 5:22 PM, Tom Duncan wrote:
Or you can rename the strsbs command.
Tom Duncan
On Sat, Mar 16, 2019 at 3:32 PM DrFranken <midrange@xxxxxxxxxxxx> wrote:
Nope. The last step of the SAVE 21 is STRSBS <controlling subsystem>
I have used three strategies:
1) Select prompt for commands and then press F12/F3 when STRSBS comes
up. Of course you need to be there to execute the commands.
2) Use my own CLP to do the save and omit the STRSBS command.
3) Change QSTRUPPGM to *NONE and be sure that The parm STRTCP on CHGIPLA
is set to *NO. This is not completely effective as scheduled jobs will
run but your users can't get on.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 3/16/2019 4:11 PM, Justin Taylor wrote:
I need to do a full save and then leave the system in a restrictedstate. Will this do it?
endsbs *all--
go save, 21
TIA
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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
