Copy a File to a New z/OS Sequential Data Set

This example copies, in text mode, a file from a remote UNIX system to a sequential data set on z/OS. The data set does not exist on z/OS; UDM is instructed to create it.

The data set is dynamically allocated based on the local UDM dynamic allocation attributes. UDM provides default attributes that can be changed to meet local requirements. The UDM defaults, as they are delivered, create a sequential, variable block record data set with a logical record length of 1024.

The sample below changes the record length to 256 in order to demonstrate how to set dynamic allocation attributes.

A DD file system sample is not provided, since creating a new data set with JCL is the same in UDM as it is in any batch application. There are no UDM specific requirements.

DSN File System

//S1     EXEC UDMPRC
//UNVSCR DD *
1 /wiki/spaces/UA73/pages/3769053 _echo=yes _halton=warn
2 /wiki/spaces/UA73/pages/3769059 unix=sol9 user=top098 pwd=p100m
3 /wiki/spaces/UA73/pages/3778454 unix=/opt/app/data
4 /wiki/spaces/UA73/pages/3778428 type=text
5 /wiki/spaces/UA73/pages/3768947 local lrecl=256
6 /wiki/spaces/UA73/pages/3778455 data10.txt local='app.data.daily'
7 /wiki/spaces/UA73/pages/3769057 
/*

Almost all data set allocation attributes can be specified as UDM attributes, providing you with the ability to dynamically allocate any supported data set.

Care should be taken that conflicting allocation attributes are not specified. The results of the allocation should be check to verify they meet your intentions. Although UDM checks attribute values, some values are provided by the system from sources that UDM cannot verify and can result in invalid or unintentional attribute combinations.

Components

/wiki/spaces/UA73/pages/3768704