BMC AMI Copy data sets


BMC AMI Copy uses an input data set (SYSIN) and a print data set (SYSPRINT) that are both specified by a data definition name (DDName) in the BMC AMI Copy JCL.

Each output copy data set can also be allocated by a DDName in the JCL or allocated dynamically by BMC AMI Copy. If the dynamic allocation is used, an optional data set, ACPGDG, can be specified to provide a GDG model that is applied if a GDG base does not exist. ACPGDGLP, ACPGDGLB, ACPGDGRP, and ACPGDGRB can be specified for the GDG bases by copy type.

When BMC AMI Copy uses multitasking, it allocates one data set for the output from each subtask. The DD name for each of these data sets is ACPPRT nn, where nn is the subtask number.

ACPERROR (and ACPERR nn for multitasking) are optional output data sets to which messages of type E and W are written.

Instant Snapshot copies are made using intelligent storage devices and are VSAM files for which the data component is determined by the hardware interface. BMC AMI Copy syntax specifies the VSAM cluster name.

To see the relationships of the data sets to the processing phases of BMC AMI Copy, see BMC-AMI-Copy-COPY-and-MODIFY-processing-phases.

For more information about BMC AMI Copy data sets, see Allocating-output-copy-data-sets-dynamically and BMC-AMI-Copy-data-set-DD-statements.

The following table describes the BMC AMI Copy data sets:

Data set

COPY command

COPY IMAGECOPY command

RECALL command

QUIESCE command

MODIFY command

SYSIN

  • SYSIN is the input data set containing the BMC AMI Copy commands and options. 1
  • All commands can be mixed in the same SYSIN statement.
  • Unicode is not supported in the SYSIN file. 2

ACPGDG

  • ACPGDGLP
  • ACPGDGLB
  • ACPGDGRP
  • ACPGDGRB
  • ACPGDG is an optional input data set that can be used with dynamic allocation to create a GDG base if one does not exist. This data set contains the control cards to perform an IDCAMS DEFINE and the symbolic variable &BASE.
  • ACPGDGLP, ACPGDGLB, ACPGDGRP, and ACPGDGRB can be used to specify the GDG bases by copy type. BMC AMI Copy looks for these first and if they are not found, uses ACPGDG.

Not applicable

Not applicable

Not applicable

Output Image Copies 3

  • These data sets can be allocated dynamically or by DDName in the JCL
  • The default DDName for the first copy is SYSCOPY when allocated in the JCL
  • The DDName can be changed using COPY command options
  • More copy data sets can be specified
  • These data sets are used during the COPY phase of command processing

Not applicable (no output copies are made)

Not applicable

Not applicable

SYSPRINT

  • SYSPRINT is the output data set for BMC AMI Copy messages.
  • SYSPRINT is used during all BMC AMI Copy phases and is also used by any other process invoked by BMC AMI Copy.
  • If SYSPRINT is not defined as SYSOUT in the JCL, BMC AMI Copy forces the disposition of the data set to MOD.
  • BMC AMI Copy displays Unicode names that do not translate to EBCDIC as UTF-8 (Unicode Transformation Format, 8-bit encoding form) representation in hexadecimal.
  • BMC AMI Copy displays table names, index names, and creator names that can be up to 128 bytes long. Output messages with such names can print on multiple lines.

ACPPRT nn

Output messages when multitasking (MAXTASKS > 1); one needed per subtask. If no DD statement is coded, BMC AMI Copy will dynamically allocate to SYSOUT.

Not applicable

Not applicable

Not applicable

ACPERROR

ACPERROR is an optional data set to which W and E message type messages can be written.

Not applicable

ACPERR nn

ACPERR nn, where nn is the task number, is an optional data set used when multitasking (MAXTASKS>1); one is needed by subtask. If the ACPERROR DD statement is coded in the JCL, ACPERR nn data sets are dynamically allocated. W and E message type messages are written to ACPERR nn data sets.

Not applicable

1 See Command-and-syntax-reference for descriptions of the BMC AMI Copy commands and options. Long-names give specific information about using long names in SYSIN.

2 BMC AMI Copy can process objects with Unicode names. However, indexes must be included using the COPY INDEXSPACE command or INDEXES YES parameter. BMC AMI Copy commands that use wildcards do not include objects that have non-translatable (to EBCDIC) Unicode characters in the wildcard position. This is because SYSIN is EBCDIC and wildcard processing is done in EBCDIC.

3 Instant Snapshot copies, which are specified using DSSNAP YES on the OUTPUT command, are VSAM cluster files. The data component is named by the hardware implementation. The data sets are allocated dynamically by the hardware interface.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*