Comments on: Option 21 save on IBM iSeries

By: cabrr

cabrr — Fri, 11 Jun 2010 19:16:01 +0000

WPOULIN,
This is what I have been waiting for. I appreciate all of the other comments, but I already knew all of that.
Thanks , cabrr

By: wpoulin

wpoulin — Fri, 11 Jun 2010 18:44:52 +0000

Cabrr,

The actual CL Program that is executed behind option 21 is QMNSAVE in the QSYS library. If you do a RTVCLSRC you can see the actual code that is used.

Hope this helps,
Bill Poulin

By: security1

security1 — Thu, 10 Jun 2010 16:23:01 +0000

Cabrr This is what occurring while Option 21 (SAVALL) is running. Select this option to save the entire system (except contents of message, job, output, and data queues.) This option performs the following operations: Starts the save immediately Changes the system operator (QSYSOPR) message queue to *BREAK or *NOTIFY delivery mode Ends all subsystems Backs up: Licensed internal code The system library (QSYS) Security objects, including user profiles Device configuration objects All IBM-supplied libraries including those containing user data All user libraries All mail All folders All documents All objects in directories Starts the controlling subsystem This option runs the following commands: 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)

By: woodengineer

woodengineer — Thu, 10 Jun 2010 16:17:56 +0000

There are many commands executed by an Option 21 save. Be aware that all system activity must be stopped during this save because it saves everything.

If there are custom sub-systems running on your system, those need to be stopped manually. For example, we run ASNA’s DataGate products, which run in their own sub-sytems. Even though the documentation says that all sub-systems are ended, we discovered that custom sub-systems did not end, which caused the save to hang up. Once we manually ended those sub-systems the save started running.