Page Comparison

 
Specifies whether American Standards Association (ASA) print control characters are translated for data sets whose record format includes an A (for example: FA, FBA, VBA).

Controls byte order mark (BOM) processing for UTF16-encoded output files.
 
When a file is written using one of the UTF-16 encodings - UTF-16, UTF-16LE, or UTF-16BE - the bom attribute specifies whether or not a byte order mark (BOM) should be included at the start of the output file.
 
If the value of bom is default, then the conversion routines decide whether or not a BOM is included in the output file. This value is provided for compatibility with the UDM 6.2.0 release, which introduced UTF-16 conversions, but did not provide BOM handling.
 
The behavior when bom=default is:

Specification for how the file is to be created:

<ul> <li>

• If

• value

• is

• append,

• the

• transferred

• data

• is

• appended

• to

• any

• data

• already

• in

• an

• existing

• destination

• file.

• If

• the

• destination

• file

• does

• not

• exist,

• it

• is

• created.

• If

• value

• is

• new,

• the

• UDM

• copies

• the

• file

• only

• if

• the

• destination

• file

• does

• not

• already

• exist.

• If

• the

• destination

• file

• does

• exist

• at

• the

• time

• the

• copy

• operation

• is

• initiated,

• the

• operation

• returns

• with

• an

• error.

• If

• value

• is

• replace,

• UDM

• overwrites

• an

• existing

• destination

• file.

• Otherwise,

• UDM

• creates

• the

• file.

Default is new.

Sequence of characters appended to the end of the filename used to write the destination file, if the source filename is being used implicitly as the destination filename. This occurs after the file extension has been truncated (if truncext is set to yes).
 
By default, no default extension is defined.

End-of-line sequence used in text transfers.
 
For the source side of a copy operation, excepting those from the z/OS dd and dsn file systems and the IBM i lib file system, the end-of-line sequence is used to determine the end of each line of data. When the specified sequence occurs in the data, UDM considers all data read up to that point (starting from the previous line) as a single line. Each line is transferred without the end-of-line sequence.
 
On the destination side of a text transfer, the end-of-line sequence is appended to the end of each line before it is written.
 
Two special character sequences can be used in any end of line sequence:

Line operation for transferred lines (records under the z/OS dd and dsn file systems).
 
For the line operation to be in play in the transfer, the value of linelen must not be zero (linelen is set automatically for the z/OS dd and dsn file systems to the logical record size if it is zero).

<ul> <li>

• If

• value

• is

• none,

• each

• source

• line

• or

• record

• or

• data

• is

• written

• as

• it

• is

• received

• as

• a

• complete

• line

• or

• record.

• If

• the

• length

• of

• the

• source

• line

• is

• greater

• than

• that

• specified

• by

• *linelen*,

• UDM

• issues

• an

• error

• and

• the

• transfer

• operation

• is

• aborted.

• If

• value

• is

• stream,

• the

• source

• data

• is

• treated

• as

• one

• long,

• single

• line

• of

• data.

• The

• source

• data

• is

• broken

• into

• multiple

• lines

• (records),

• each

• with

• a

• length

• of

• that

• specified

• by

• linelen.
• If value is trunc, each source line longer than the value specified by linelen is truncated to be exactly linelen characters long.
• If value is wrap, each source line longer than the value specified by linelen is broken up into multiple lines, each no longer than linelen characters long. Each segment is written out as a separate line (record).

 
(By default, the lineop attribute is not defined.)

 
Specification for the mode (in UNIX parlance), or file permissions, of a file created by UDM in a copy operation. Existing files do not have their modes modified by UDM. They retain the file mode that they had before the copy operation was initiated.
 
Each number in the set corresponds to one or more individuals for whom access is granted for the file:

<ul> <li>

• First

• number:

• Owner

• of

• the

• file.

• Second

• number:

• Users

• in

• the

• group

• assigned

• to

• the

• file.

• Third

• number:

• Everyone

• else.

 
The value of each number is the sum of values representing file permissions:

<ul> <li>

• 0

• -

• No

• permissions.

• 1

• -

• Permission

• to

• execute

• the

• file.

• 2

• -

• Permission

• to

• write

• to

• the

• file.

• 4

• -

• Permission

• to

• read

• from

• the

• file.

 
(By default, the mode attribute is not set. The default mode of a newly created file by UDM is dependent upon the user's umask or the mode of the source file in a UDM transfer.)

Specification for whether or not data is padded. (Used in conjunction with linelen, when linelen is not zero.)

<ul> <li>

• If

• value

• is

• none,

• each

• line

• (record)

• of

• data

• written

• is

• not

• padded.

• If

• value

• is

• null,

• each

• line

• of

• data

• is

• padded

• with

• null

• characters

• (hex

• value

• 0)

• at

• the

• end

• until

• the

• line

• is

• linelen characters

• in

• length.

• If

• value

• is

• space,

• each

• line

• of

• data

• is

• padded

• with

• spaces

• at

• the

• end

• until

• the

• line

• is

• linelen characters

• in

• length.

 
Default is none.

Specifies how to manage files whose records may start with a 4-byte Record Descriptor Word (RDW). This RDW contains the record length for variable-length record data that originates from z/OS, and is structured as follows:

<ul> <li>

• Bytes

• 1

• &

• 2
  Length

• of

• the

• logical

• record,

• including

• the

• 4-byte

• RDW.

• Byte 3
  A segment flag,

• with

• the

• following

• values:

• • 0 - Complete record contained in a single logical record.
  • 1 - Logical record is split across multiple segments, and this is the first.
  • 2 - Logical record is split across multiple segments, and this is the last.
  • 3 - Logical record is split across multiple segments, and this is a middle record.
• Byte 4
  Unused

The role that the rdw attribute plays varies depending on context.
 
For files transferred from z/OS:

<ul> <li>

• If

• the

• value

• is

• yes,

• the

• 4

• bytes

• of

• the

• RDW

• are

• stored

• in

• the

• destination

• file.

• If

• the

• value

• is

• no,

• the

• RDW

• is

• stripped

• from

• the

• record

• prior

• to

• transfer

• and

• is

• not

• stored

• in

• the

• destination

• file.

For files transferred to z/OS:

<ul> <li>

• If

• the

• value

• is

• yes,

• UDM

• recognizes

• that

• the

• input

• file

• contains

• one

• or

• more

• logical

• records,

• and

• that

• the

• first

• 4

• bytes

• of

• each

• those

• records

• is

• an

• RDW.

• The

• length

• of

• each

• logical

• record

• is

• used

• to

• deliver

• separate

• physical

• records

• to

• the

• z/OS

• system.

• To

• have

• the

• logical

• records

• stored

• as

• physical

• records

• on

• z/OS,

• you

• must

• set

• the

• linelen and lineop attributes.

• linelen

• should

• be

• the

• dataset's

• record

• length

• minus

• 4,

• and

• lineop

• must

• be

• wrap

• (for

• example,

• attrb

• dst

• linelen=LRECL-4

• lineop=wrap,

• where

• LRECL

• is

• the

• record

• length

• specified

• in

• the

• dataset's

• DCB

• info).

• 
  
  When

• the

• records

• are

• sent

• back

• to

• z/OS,

• the

• RDW

• is

• removed

• from

• the

• data.

• The

• new

• records

• receive

• an

• RDW

• from

• the

• OS

• as

• the

• dataset

• is

• written.

• 
  
  
• If

• the

• value

• is

• no,

• UDM

• will

• not

• apply

• any

• special

• handling

• to

• the

• records

• and

• will

• transfer

• them

• as-is.

The default is no.
 

Allows regular expression pattern matching to select which files are chosen for the copy, delete, dir, and move commands, and the forfiles.
 
If the value of this attribute is yes, file names specified for the corresponding session are processed in a grep-like fashion. Care must be taken when crafting the expression to ensure that only the files desired are processed.
 
For example, given the script commands:
 

<pre>
open src=somehost user=uid pwd=pwd
attrib src regex=yes

cd src=d:\rootdir\datadir
copy src=^[AaBb]
</pre>

 
Any files in d:\rootdir\datadir that contain the substring 123.txt - including the file named 123.txt - will be copied.
 
Use regular expression control characters such as ^ and $ to limit the substring to match the beginning and ending of file names. For example, use ^123.txt$ to copy just the file named 123.txt. Additional information on regular expressions, including the different matching patterns that are available, can be found in a number of online resources and UNIX man pages.
 
Also, remember that wildcards are treated as special control characters in regular expressions. Set this attribute to no or omit it entirely to have UDM process wildcard characters as a "true" wildcard.
 
Default is no.
 

 
Specification for whether or not the creation timestamp of the destination file in a copy operation matches the creation timestamp of the source file.

<ul> <li>

• If

• value

• is

• yes,

• the

• creation

• timestamp

• of

• the

• destination

• file

• matches

• the

• creation

• timestamp

• of

• the

• source

• file.

• If

• the

• value

• is

• no,

• the

• creation

• timestamp

• of

• the

• destination

• file

• does

• not

• match

• the

• creation

• timestamp

• of

• the

• source

• file.

 
Default is no.

 
Specification for whether or not the modification timestamp of the destination file in a copy operation matches the modification timestamp of the source file.

 
Specification for whether or not the last access timestamp of the destination file in a copy operation matches the last access timestamp of the source file prior to the copy operation.

<ul> <li>

• If

• value

• is

• yes,

• the

• last

• access

• timestamp

• of

• the

• destination

• file

• matches

• the

• last

• access

• timestamp

• of

• the

• source

• file

• prior

• to

• the

• copy

• operation.

• If

• the

• value

• is

• no,

• the

• last

• access

• timestamp

• of

• the

• destination

• file

• does

• not

• match

• the

• last

• access

• timestamp

• of

• the

• source

• file

• prior

• to

• the

• copy

• operation.

 
Default is no.

Specification for whether or not a transactional file copy is to be performed: