How do I specify an MVS data set name when using lftp?
up vote
2
down vote
favorite
We have a Linux server that needs to send a file to a z/OS mainframe using FTPS. How do we specify the MVS data set name we want to create? When we try to FTP the file, it always prepends the mainframe user ID to the data set name.
ftps lftp mainframe zos
add a comment |
up vote
2
down vote
favorite
We have a Linux server that needs to send a file to a z/OS mainframe using FTPS. How do we specify the MVS data set name we want to create? When we try to FTP the file, it always prepends the mainframe user ID to the data set name.
ftps lftp mainframe zos
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
We have a Linux server that needs to send a file to a z/OS mainframe using FTPS. How do we specify the MVS data set name we want to create? When we try to FTP the file, it always prepends the mainframe user ID to the data set name.
ftps lftp mainframe zos
We have a Linux server that needs to send a file to a z/OS mainframe using FTPS. How do we specify the MVS data set name we want to create? When we try to FTP the file, it always prepends the mainframe user ID to the data set name.
ftps lftp mainframe zos
ftps lftp mainframe zos
edited Nov 16 at 7:33
Adam Limbert
169112
169112
asked Oct 12 at 18:44
Matt
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
For FTP transfers to z/OS there are a few considerations. First, there are two types of files you can send data to: MVS files and USS files.
MVS files are the traditional types of files on z/OS and have a format of hlq.qual1.qual2.qual3....
. USS files are saved in a format that is similar to Unix file systems. FTP can send files to both types.
For USS files you would simply follow regular FTP conventions:
cd /targetDir
bin
choose the transfer method of binary or textput myfile
There is a whole discussion around encoding and translation which I'll defer.
For MVS files you follow a similar sequence except that MVS requires more information about the file like its attributes:
cd "USER1.MYFILES" - this would change to a prefix which is prepended to the file being transferred. Note you can specify any prefix, not only userid. For instance, you could use
cd PROD.NEWDATA` which would create a file prefixed with PROD.NEWDATA.fileName
bin
chooses the transfer method
Now you can provide information about the file attributes using the Site Command
For example:
* site 'LRECL=80 RECFM=FB BLKSIZE=3120 CYLINDERS'
which tells MVS how to save the file.
Then you can send the file:
put localFileName LOCALFIL
The resulting file would be stored as USER.MYFILES.LOCALFIL
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
For FTP transfers to z/OS there are a few considerations. First, there are two types of files you can send data to: MVS files and USS files.
MVS files are the traditional types of files on z/OS and have a format of hlq.qual1.qual2.qual3....
. USS files are saved in a format that is similar to Unix file systems. FTP can send files to both types.
For USS files you would simply follow regular FTP conventions:
cd /targetDir
bin
choose the transfer method of binary or textput myfile
There is a whole discussion around encoding and translation which I'll defer.
For MVS files you follow a similar sequence except that MVS requires more information about the file like its attributes:
cd "USER1.MYFILES" - this would change to a prefix which is prepended to the file being transferred. Note you can specify any prefix, not only userid. For instance, you could use
cd PROD.NEWDATA` which would create a file prefixed with PROD.NEWDATA.fileName
bin
chooses the transfer method
Now you can provide information about the file attributes using the Site Command
For example:
* site 'LRECL=80 RECFM=FB BLKSIZE=3120 CYLINDERS'
which tells MVS how to save the file.
Then you can send the file:
put localFileName LOCALFIL
The resulting file would be stored as USER.MYFILES.LOCALFIL
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
add a comment |
up vote
2
down vote
For FTP transfers to z/OS there are a few considerations. First, there are two types of files you can send data to: MVS files and USS files.
MVS files are the traditional types of files on z/OS and have a format of hlq.qual1.qual2.qual3....
. USS files are saved in a format that is similar to Unix file systems. FTP can send files to both types.
For USS files you would simply follow regular FTP conventions:
cd /targetDir
bin
choose the transfer method of binary or textput myfile
There is a whole discussion around encoding and translation which I'll defer.
For MVS files you follow a similar sequence except that MVS requires more information about the file like its attributes:
cd "USER1.MYFILES" - this would change to a prefix which is prepended to the file being transferred. Note you can specify any prefix, not only userid. For instance, you could use
cd PROD.NEWDATA` which would create a file prefixed with PROD.NEWDATA.fileName
bin
chooses the transfer method
Now you can provide information about the file attributes using the Site Command
For example:
* site 'LRECL=80 RECFM=FB BLKSIZE=3120 CYLINDERS'
which tells MVS how to save the file.
Then you can send the file:
put localFileName LOCALFIL
The resulting file would be stored as USER.MYFILES.LOCALFIL
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
add a comment |
up vote
2
down vote
up vote
2
down vote
For FTP transfers to z/OS there are a few considerations. First, there are two types of files you can send data to: MVS files and USS files.
MVS files are the traditional types of files on z/OS and have a format of hlq.qual1.qual2.qual3....
. USS files are saved in a format that is similar to Unix file systems. FTP can send files to both types.
For USS files you would simply follow regular FTP conventions:
cd /targetDir
bin
choose the transfer method of binary or textput myfile
There is a whole discussion around encoding and translation which I'll defer.
For MVS files you follow a similar sequence except that MVS requires more information about the file like its attributes:
cd "USER1.MYFILES" - this would change to a prefix which is prepended to the file being transferred. Note you can specify any prefix, not only userid. For instance, you could use
cd PROD.NEWDATA` which would create a file prefixed with PROD.NEWDATA.fileName
bin
chooses the transfer method
Now you can provide information about the file attributes using the Site Command
For example:
* site 'LRECL=80 RECFM=FB BLKSIZE=3120 CYLINDERS'
which tells MVS how to save the file.
Then you can send the file:
put localFileName LOCALFIL
The resulting file would be stored as USER.MYFILES.LOCALFIL
For FTP transfers to z/OS there are a few considerations. First, there are two types of files you can send data to: MVS files and USS files.
MVS files are the traditional types of files on z/OS and have a format of hlq.qual1.qual2.qual3....
. USS files are saved in a format that is similar to Unix file systems. FTP can send files to both types.
For USS files you would simply follow regular FTP conventions:
cd /targetDir
bin
choose the transfer method of binary or textput myfile
There is a whole discussion around encoding and translation which I'll defer.
For MVS files you follow a similar sequence except that MVS requires more information about the file like its attributes:
cd "USER1.MYFILES" - this would change to a prefix which is prepended to the file being transferred. Note you can specify any prefix, not only userid. For instance, you could use
cd PROD.NEWDATA` which would create a file prefixed with PROD.NEWDATA.fileName
bin
chooses the transfer method
Now you can provide information about the file attributes using the Site Command
For example:
* site 'LRECL=80 RECFM=FB BLKSIZE=3120 CYLINDERS'
which tells MVS how to save the file.
Then you can send the file:
put localFileName LOCALFIL
The resulting file would be stored as USER.MYFILES.LOCALFIL
answered Oct 12 at 21:50
Hogstrom
1,1421120
1,1421120
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
add a comment |
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
2
2
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
Thanks for the help, you have me going in the right direction.
– Matt
Oct 12 at 22:54
2
2
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
Thanks, if you need further clarification let me know. If this works, mark it as useful if it answers your question.
– Hogstrom
Oct 13 at 0:29
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1366314%2fhow-do-i-specify-an-mvs-data-set-name-when-using-lftp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown