z/OS DFSMS OAM Application Programmer's Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


STOREPRT—Storing an individual part in a Store Sequence operation

z/OS DFSMS OAM Application Programmer's Reference
SC23-6865-00

Use one or more STOREPRT requests to store each individual part of the object following the prerequisite STOREBEG. For each STOREPRT, you must provide the store token that OAM uses to obtain information about this particular store request initiated with STOREBEG. You must specify the OFFSET where this part of the object is to be stored; for the first STOREPRT this offset must be 0 and for each subsequent STOREPRT, this offset must be the next byte following the previously stored part. Each part of the object therefore must be stored contiguously, in order, with no overlapping from beginning to end. The SIZE specified on STOREPRT indicates the size of the part of the object that is being stored. Note that this part of the object should be contained in either a single buffer or multiple contiguous buffers. It is suggested that the object be stored in as few parts as possible, because of the overhead involved in individually storing each part of the object. The minimum size for each part is 1 megabyte (1,048,576), except for the last part of the object. STOREBEG, STOREPRT and STOREEND cannot be used for objects with a total size less than or equal to 50 megabytes.

Read syntax diagramSkip visual syntax diagram
Syntax for OSREQ STOREPRT

>>-OSREQ STOREPRT--MF=-+-L---------------------------------+---->
                       +-(M,parameter_list-+-----------+-)-+   
                       |                   '-,COMPLETE-'   |   
                       '-(E,parameter_list-+-----------+-)-'   
                                           '-,COMPLETE-'       

>--+-------------------------------------+---------------------->
   |       (1)                           |   
   '-TOKEN----=-+-token_area-----------+-'   
                '-(token_area_pointer)-'     

>--+---------------------------------------+-------------------->
   |        (1)                            |   
   '-STOKEN----=-+-store_token-----------+-'   
                 '-(store_token_pointer)-'     

>--+-----------------------------------------+------------------>
   |      (1) (2)                            |   
   '-SIZE--------=-+-object_byte-----------+-'   
                   '-(object_byte_pointer)-'     

>--+-------------------------------------------------------+---->
   |        (1) (3)                                        |   
   '-OFFSET--------=-+-offset_of_starting_byte-----------+-'   
                     '-(offset_of_starting_byte_pointer)-'     

>--+--------------------------------------------+--------------->
   |         (1) (4)                            |   
   '-BUFLIST--------=-+-buffer_list-----------+-'   
                      '-(buffer_list_pointer)-'     

>--+-----------------+------------------------------------------>
   '-RELBUF=-+-YES-+-'   
             '-NO--'     

>--+-------------------------------------+---------------------->
   '-MSGAREA=-+-message_area-----------+-'   
              '-(message_area_pointer)-'     

>--+------------------------------------+----------------------->
   '-RETCODE=-+-return_code-----------+-'   
              '-(return_code_pointer)-'     

>--+------------------------------------+----------------------->
   '-REACODE=-+-reason_code-----------+-'   
              '-(reason_code_pointer)-'     

>--+--------------------------------------+--------------------><
   '-TTOKEN=-+-tracking_token-----------+-'   
             '-(tracking_token_pointer)-'     

Notes:
  1. These keywords are required and therefore they must be specified on the MF=E form if it indicates COMPLETE or they must be specified on at least one of the forms if the MF=E does not indicate COMPLETE.
  2. The size specified must be the size of just this part of the object being stored.
  3. The offset must be zero for the first part stored for the object, and for each subsequent store you must identify the offset of the next byte immediately following the previous part stored for the object (that is, the sum of the offset and size for the previous part stored).
  4. The buffers provided must be contiguous and it is recommended that the amount of object data provided on each STOREPRT is maximized to minimize the number of individual STOREPRT requests.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014