Packaging and distribution considerations

 

When working with the packaging function, keep these considerations in mind.

• The packaging function that does not use a snapshot, stores temporary save files in the QRPLOBJ library. These files are prefixed with QYDS. The packaging function that uses a snapshot stores temporary save files in the QUSRSYS library. (A snapshot is a file that contains the data at a particular instant in time for all the files that were selected to be in a package. Creating a snapshot allows you to capture the contents of the selected files at a given time and then distribute that version of the files at a future time. )

• Typically, the QRPLOBJ library is cleaned up when an IPL is done. However, if between IPLs, the temporary storage that is used in QRPLOBJ is a concern, you can use the following commands to view and clear the objects that are in this library.

  DSPLIB LIB(QRPLOBJ) 
  WRKOBJPDM LIB(QRPLOBJ) OBJ(*ALL) 
  WRKOBJPDM LIB(QRPLOBJ) OBJ(QYDS*) OBJTYPE(*FILE) OBJATR(*SAVF) 
  CLRLIB LIB(QRPLOBJ)

• The packaging function allows you to send and restore QSYS objects, QSYS libraries, integrated file system directories, and integrated file system files.

• Database files with referential constraints might not work properly because of sequence dependency. Additionally, database files with referential constraints behave differently depending on whether the database file that is being distributed is being replaced or is a new file. Thus the packaging function does not support sending database files when there is a dependency on the sequence in which the files are restored (such as logical database files).

• The packaging function does not support IASP distributions.

• You cannot use Management Central to distribute CUM tapes/packages.

• Packaging was not designed for very large distributions. A long duration of time maybe required to send very large save files to the target systems. If the size of the files (save file or snapshot size) is over 1 gigabyte, then you should run tests in your environment to determine if the time that is required to perform the distribution to the target systems is acceptable.

  As an alternative, you might want to send very large files between systems is to use FTP. This can be faster.

• You cannot distribute the latest i5/OS™ release, or migrate to a later release using Management Central. LPPs and Base i5/OS Options can be distributed and installed, but not Base i5/OS (QSYS and SLIC).

• You cannot mix QSYS and integrated file system files in a single package. Management Central uses the save/restore function, and is therefore bound by the restrictions that it imposes regarding mixing different file systems.

  You can create a package containing QSYS files and another one containing integrated file system files, and then send each package to an endpoint system. But, you cannot combine them into a single package.

  As a work around you can place the integrated file system objects into a save file. Then include the save file with your QSYS objects. Next, perform the restore of the save file to integrated file system objects. Or you can use the post command capability in the package definition to do the restore.

• You can refresh the snapshot by right-clicking on the package definition and selecting 'Update Snapshot' from the context menu. However, remember to resend the package to the systems that you want the updates on after you have updated the snapshot.

• Save and restores are performed under the user profile of the user that is signed on to iSeries™ Navigator. The post distribution command runs under the user profile of the person who started the distribution (the person that is signed on to iSeries Navigator). The job description that is used is QSYS/QYPSJOBD.

• If you are distributing a QSYS object that you created, then you will need *RWX authority to the QRPLOBJ library on both the source and the target systems. If someone else created the object, then you might need additional authorities. Authority to RSTOBJ is required when you are sending all of the objects from a library.

  If the package that you are distributing is an integrated file system file that you have created, then you do not need any additional authorities.

• In V5R2 and earlier, the package function runs under the C++ server QYPSSRV. In V5R3 and later, the package functions runs under the Java™ server QYPSJSVR. Thus, if your central system is V5R3 or later, you cannot create a snapshot on a V5R2 or earlier source system. In this special situation the QYPSJSVR server is not able to properly communicate with the V5R2 source QYPSSRV server. Nonetheless, you can still send a package from a V5R2 source system to a target system running V5R3 or later.

 

Parent topic:

Using other features of Management Central