チェックポイント ファイルの割り当て

 If any of the following applies, a checkpoint file of.
cmfzs10jp
 If any of the following applies,
CA MIM for z/OS
a checkpoint file of.
  • When using CTCONLY intersystem communication method. In this environment, the local checkpoint file of each system is used to store the status information of the MIMplex system.
  • When using XCF system communication method. In this environment, the local checkpoint file of each system is used to store the status information of the MIMplex system.
  • When using ECMF job re-queue function. In this case, a local checkpoint file is used to keep track of the information associated with batch jobs that are pending (re-queued) by ECMF.
:
  • If you do not know whether to assign a checkpoint file at this point, we recommend that you assign it. If you decide not to use
    CA MIM for z/OS
    the checkpoint file required
    CA MIM for z/OS
    function, you can delete the assigned checkpoint file at a later time.
  •  
    CA MIM for z/OS
    Checkpoint file
    CA MIM for z/OS
    can not be shared in the address space between multiple systems . For each MIMplex system, at least one checkpoint file is required.
  •  
    CA MIM for z/OS
    Checkpoint files need not be assigned to shared DASD volumes.
  •  
    CA MIM for z/OS
    Serializes access to the checkpoint file by issuing an ENQ SCOPE = SYSTEM request. Hardware RESERVE requests are not issued. In other applications, you
    CA MIM for z/OS
    can place a checkpoint file on a DASD device with other data sets, unless you issue a Hardware Reserve request to the selected DASD unit .
IMPORTANT:
CA MIM for z/OS
We do not support checkpoint files at elevated locations on Extended Address Volumes (EAV). When using EAV, be sure to allocate dataset using EATTR = NO.
How to assign a checkpoint file
  1. Customize and submit the job of CAI.CBTDJCL (ALLOCKPT) member. This member also contains other useful things.
  2. CAI.CBTDPARM (MIMINIT)
    CA MIM for z/OS
    Add the ALLOCATE command to the parmlib member .
    This
    CA MIM for z/OS
    assigns a new checkpoint file to the address space at startup .
note:
  • CA MIM for z/OS
    The usual naming convention for checkpointing files uses the system name as one of the dataset name's nodes.
  • In this procedure
    CA MIM for z/OS
    you can also assign one or more checkpoint files to only one system and use to expand the copy to each MIMPlex system.
  • CA MIM for z/OS
    For details on the checkpoint file and other intersystem communication methods, see CA MIM Programming .