Loading an image, using call IMARST

GDDM V3R2 Base Application Programming Guide

Loading an image, using call IMARST

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

The image saved by the IMASAV example in the previous section can be loaded from auxiliary storage to a device or application image, using the IMARST call. Here is an example:


     DCL DESCR CHAR(30);     /* File description              */
     /*         ID   PROJ  FILENAME   STR.LEN. DESCRIPTION    */
     CALL IMARST(0,   0,   'MYIMAGE',   30,       DESCR);

The parameters are similar to those of the IMASAV call. The first parameter of the IMARST call specifies an identifier for the image into which a saved image is to be restored. The value 0 used in the example specifies that the saved image is to be restored to the display. Alternatively, you can restore an image to an application image.

If you have created a projection (see "Creating a projection using call IMPCRT" in topic 6.5.2), you can supply its identifier on the second parameter of the IMARST call to apply it to the image as it is restored. The call in this example applies the identity projection.

To restore the description of a saved image you need to specify the number of characters you want returned from the description, (30 in this case), and then supply a variable name into which these characters are to be returned.

Saving and restoring are transfer operations. You can, therefore, apply a projection during either or both of the operations.

That completes the description of the calls used in the first example, but, before you learn more about projections, here are two calls that were not used in the example:

Notices | Terms of use | Support | Contact z/OS