The backupConfig command is delivered inside of the WebSphere product on the iSeries that allows the WebSphere configuration to be backed up and used to restore your WebSphere applications if your WebSphere environment becomes corrupt or damaged. The problem is this command is a Qshell command and has Qshell output that makes it difficult for you to submit this command unattended. We needed to be able to execute this command from a CL program that could be submitted as a scheduled job or before some extensive WebSphere configuration changes are to be done, without having to get into Qshell.
Another important point to note about the backupConfig command is to use the -nostop option, which allows you to backup your WebSphere applications without having to bring down any of the WebSphere subsystem jobs. The CL program that is listed below shows how to disable the Qshell from sending informational messages and then examples of backing up the node agent and the deployment manager using the backupConfig command. The CD change directory) command that is right before the backupConfig command tells where to write the backup configuration files. This CL command can be called anytime directly from a command line or entered as a scheduled job to run at certain times. The example below is from backing up a WebSphere Network Deployment version 6.0 application environment on the iSeries.
/* TELL QSHELL NOT TO DISPLAY OUTPUT ON SCREEN */ RMVENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) MONMSG MSGID(CPFA981) /* ENVVAR DOES NOT EXIST */ ADDENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) VALUE(NONE) /* EXECUTE QSHELL COMMANDS */ STRQSH CMD('cd /qibm/UserData/WebSphere/WASbackups;/qibm/U+ serData/WebSphere/AppServer/V6/ND/profiles/NUV/bin/backupC+ onfig -username admin -password admin1 -nostop;/qibm/UserData+ /WebSphere/AppServer/V6/ND/profiles/NUVDmgr/bin/backupConfig + -username admin -password admin1 -nostop) /* RESTORE DEFAULT BEHAVIOR. */ CHGENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) VALUE(STDOUT) ENDPGM