Limitations

Before you use On-Demand Environments, make sure that you are aware of the following known limitations.

JES2PARM INCLUDE Statement Limitation

When creating a system residence volume component that requires creating a new LOAD parameter member, the source JES2PARM member (from which the new LOAD parameter configure will be copied) has the following limitation on INCLUDE statements:

Only cataloged data sets can be used in INCLUDE statements. The INCLUDE statement must use one of the following formats:
  • DSName=jxxx...x
  • DSName=jxxx...x(jxxxxxxxx)
  • DSN=jxxx...x
  • DSN=jxxx...x(jxxxxxxxx)

Stock image provision version 1.0.0.2 with a data set

  • There is a known limitation when provisioning z/OS using the stock image packaged with IBM® Test Accelerator for Z v1.0.0.2 with a data set component. Use the stock image packaged with IBM Test Accelerator for Z v1.0.0.1 if you want to provision using the stock image with a data set.

Local Fix:

When the user finds that the task of restoring the data set remains unfinished, the user can cancel the provision, SSH to the target z/OS, and run the following command:
cd /usr/lpp/IBM/zos-extract/
rm feucli.el{}
ln -e 'FEUCLI' feucli.el
./feuc volinit "unit(DE00) volume(ZDT000)"
(Where DE00 should be replaced by the device number of the volume ZDT000 that can be found in the devmap that resides in the target Linux's provision directory.)
Note: /usr/lpp/IBM/zos-extract/ is the default installation directory value. You can specify your own installation directory.

At the end, restart the Tools Server and resume the provision.

Creation support

  • On-Demand Environments supports only the provisioning of monoplex-emulated z/OS environments.

Extraction of uncataloged data sets

When using the z/OS Extraction Utilities, specifically feucvoli, to find data sets from source environments for extraction, uncataloged data sets are not automatically detected and included. In cases where uncataloged data sets are needed, such as JES2 Checkpoint or JES2 spool, the disk volumes containing these data sets must be included manually, unless there are other cataloged data sets on these volumes that have already been identified. If additional volumes that contain uncataloged data sets are needed, the system programmer of the z/OS source environments must make necessary adjustments to the list of volumes.