|
To be polite, IASPs suck. They break your CL.. I would like a new system value QMAXIASP and I would like it to be shipped as *NONE. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 10/29/2004 05:10 cc PM Subject Re: is this same as savsys21? Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Thank you. Not that I am using IASP's, but it's nice to know. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/29/2004 04:05 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject Re: is this same as savsys21? What GO SAVE 21 does is to do the following: 1. Bring down all subsystems. 2. Determine what IASPs are *AVAILABLE to save. 3. SAVSYS 4. SAVLIB *NONSYS ASPDEV(*SYSBAS) 5. SAVDLO 6. SAV with all the bullshit parameters ASPDEV(*SYSBAS) The following steps occur in alphabetic order for each of the IASPs that are *AVAILABLE: 7. SAVLIB *NONSYS ASPDEV(name) 8. SAV with all the bullshit parameters ASPDEV(name) Then: 9. RTVSYSVAL QCTLSBSD 10. Start that subsystem You can retrieve the programs that do this in QSYS. Look for QMNRSTE, QMNSAVE and QMNSRBND. Please note that this is not CL 101, so not for the faint of heart. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 10/29/2004 03:46 cc PM Subject Re: is this same as savsys21? Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I wish you wouldn't call it "savsys21". Kinda confuses it with a simple SAVSYS, don't you think? >From the online help: This option runs the following command ENDSBS SBS(*ALL) OPTION(*IMMED) SAVSYS SAVLIB LIB(*NONSYS) ACCPTH(*YES) SAVDLO DLO(*ALL) FLR(*ANY) SAV OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT) UPDHST(*YES) STRSBS SBSD(controlling-subsystem) How do they "Save available IASP's" Al? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Jerry <jdraper@xxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/29/2004 01:23 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Fax to Subject is this same as savsys21? After performing a controlled shutdown to a restricted state the following commands are run in a cl pgm. /* STEP 3: SAVE ALL SYSTEM AND NON-SYSTEM LIBRARIES */ SAVSYS DEV(&DEVICE) ENDOPT(*LEAVE) CLEAR(*ALL) + DTACPR(*NO) /* Save the system stuff */ SAVLIB LIB(*NONSYS) DEV(&DEVICE) ENDOPT(*LEAVE) + CLEAR(*AFTER) ACCPTH(*YES) DTACPR(*NO) /* + Save the user stuff */ /* STEP 4: SAVE ALL DOCUMENTATION OBJECTS */ /********************************************************************/ SAVDLO DLO(*ALL) DEV(&DEVICE) ENDOPT(*LEAVE) + CLEAR(*AFTER) DTACPR(*NO) /* Save the + documents */ /* STEP 5: SAVE ALL FILE SYSTEM OBJECTS NOT ALREADY SAVED */ /********************************************************************/ SAV DEV('/QSYS.LIB/HACTPD00.DEVD') OBJ(('/*' + *INCLUDE) ('/QSYS.LIB' *OMIT) ('/QDLS' + *OMIT)) ENDOPT(*UNLOAD) UPDHST(*YES) /* + Is this sequence equivalent to a savsys21 from the go save menu> TIA, Jerry Draper -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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
