Expiry Date = catalog

A discussion of Co:Z sftp, a port of OpenSSH sftp for z/OS
Post Reply
Alear123
Posts: 3
Joined: Fri Nov 04, 2016 11:13 am

Expiry Date = catalog

Post by Alear123 » Fri Nov 04, 2016 11:16 am

Hi all I'm trying to transfer a file from a unix server to a a/s 400 mainframe.

I want to allocate the file as a tape/cart with no expiry date.

To do this using Jcl on the mainframe I would do

Label=expdt=99000

How do I do this using the ls/+ settings from the unix system?

dovetail
Site Admin
Posts: 1848
Joined: Thu Jul 29, 2004 12:12 pm

Re: Expiry Date = catalog

Post by dovetail » Fri Nov 04, 2016 3:46 pm

There is currently a keyword for RETPD, but not EXPDT.
It seems like a good idea to add EXPDT, since there are some special values that tape management systems like CA-1 key off of.

(If you are customer with a support agreement, please submit a feature request ticket and we will give this priority)

TGibson
Posts: 10
Joined: Thu Jul 06, 2017 11:08 am

Re: Expiry Date = catalog

Post by TGibson » Mon Jul 10, 2017 2:29 pm

Did EXPDT= get implemented?

dovetail
Site Admin
Posts: 1848
Joined: Thu Jul 29, 2004 12:12 pm

Re: Expiry Date = catalog

Post by dovetail » Mon Jul 10, 2017 2:45 pm


TGibson
Posts: 10
Joined: Thu Jul 06, 2017 11:08 am

Re: Expiry Date = catalog

Post by TGibson » Tue Jul 11, 2017 8:07 am

I attempted to use the expdt=99000 and label=expdt=99000 for tape. Since it was ignored it wrote the tape to a system determined volume. The reason this is important is that when you write to a GDG with tape you must allow the dataset to be catalog controlled so the setup of the GDG base can scratch the entry. As it is you really can't write to tape to a GDG.

dovetail
Site Admin
Posts: 1848
Joined: Thu Jul 29, 2004 12:12 pm

Re: Expiry Date = catalog

Post by dovetail » Tue Jul 11, 2017 11:01 am

To diagnose, add this temporarily to the user's $HOME/.ssh/sftp-server.rc

export COZ_LOG=F

and then run the transfer.
In the session log/trace, there should be a DatasetHandler::bpxwdyn log message that has the complete BPXWDYN command used to allocate the data set. Please post that so that we can verify the correct allocation.

TGibson
Posts: 10
Joined: Thu Jul 06, 2017 11:08 am

Re: Expiry Date = catalog

Post by TGibson » Wed Jul 12, 2017 9:00 am

Here is what I found

DatasetHandlerÝF¨: -> bpxwdyn("alloc fi(SYS00007) reuse msg(2) da('C00605.FG.TEST.TAPE') blksize(0) expdt(99000) lrecl(3000) mount recfm(f,b) unit(tape) new catalog")
IEF233D M BC10,PRIVAT,SL,MDTFTP4,STEP1,C00605.FG.TEST.TAPE,
OR RESPOND TO IEF455D MESSAGE
DatasetHandlerÝF¨: <- bpxwdyn(rc=0)

dovetail
Site Admin
Posts: 1848
Joined: Thu Jul 29, 2004 12:12 pm

Re: Expiry Date = catalog

Post by dovetail » Wed Jul 12, 2017 9:28 am

The dynamic allocation was done with the IBM BPXWDYN utility with the parameters as shown.

I'm not sure what DFSMS ACS rules that you have or tape management system that you are using, but I would think that you answer lies there.

Tip: if you can dynamically allocate your tape correctly using the TSO ALLOC command, you should be able to use the same parameters (although with BPXWDYN) under Co:Z. Also: Co:Z does support the DATACLAS, STORCLAS, and MGMTCLAS keywords.

TGibson
Posts: 10
Joined: Thu Jul 06, 2017 11:08 am

Re: Expiry Date = catalog

Post by TGibson » Wed Jul 12, 2017 9:43 am

I worked with my mainframe storage people and found the function of EXPDT is working!!!

I misinterpreted the RMM tape information. If the dataset is catalog controlled in our case the Create Date = Expir Date will be the same and "VRS management value : CATALOG"
Thanks for the help.

Post Reply