AW: Re: RLSE does not work with PGM=FTP

2016-04-06 Thread Peter Hunkeler 
RLSE works perfectly with IEFBR14 and DISP=(,CATLG)  ;-)))

Release specified via JCL SPACE= works *if* the data set has been opened for 
OUTPUT and done at CLOSE time for non-SMS managed as well as SMS mamaged data 
sets.
With SMS-managed data set and RLSE *not* specified with SPACE=, release is done 
or not, based on the PARTIAL_RELEASE setting in the management class assigned 
to the data set. If to be done, it is done when the data set is CLOSE, or when 
the SMS' space management is run (depending on the actual setting).

I guess in your case, these were SMS-managed data sets that had a MGMTCLAS 
which specifies one of the "IMMED" type setting for the partial_release flag 
*and* you've been allocating the data sets with an IEFBR14 step (and space not 
yet being released), *then3 the data set has been written to in a follow-on 
step, finally closed ans space was released.

I could not build a case where space was actually release after being allocated 
via IEFBR14 step, neither with SMS-managed nor with non-SMS managed data sets.

--Peter Hunkeler


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-04 Thread Barry Merrill 
Thanks, John, that solved the problem.

Barry

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Sunday, April 03, 2016 11:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

On Sun, 3 Apr 2016 21:11:59 -0500, John McKown wrote:
>
>​Dr. Merrill,
>I know that I'm not in your league. But it looks to me like what you're 
>doing is allocating a DSN using JCL, but directing the FTP process to 
>write to it using dynamic allocation. So you never really open the DD 
>INFILE or do a CLOSE on it. IIRC, RLSE is done by the CLOSE operation. 
>Shouldn't your GET look more like:
>
>GET CICS2.terse +
>//DD:INFILE​ (replace
> 
And, perhaps likewise irritating, I've discovered that overriding DCB 
attributes in the DD statement are ineffective.  FTP will use those in the DSCB 
regardless.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-04 Thread R.S. 

RLSE works perfectly with IEFBR14 and DISP=(,CATLG)  ;-)))
(I had to fix it several times)

--
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-04-04 o 14:02, Vernooij, CP (ITOPT1) - KLM pisze:

RLSE is done during CLOSE of a dataset. IEFBR14 doesn't OPEN/CLOSE datasets.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 04 April, 2016 13:54
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

Is RLSE ever effective on an input DD (a DD that the program opens for input)?

Oh wait, INFILE is an output DD. Never mind.

In that case Dr. M. could look into the DD:ddname syntax now supported by FTP.

It's also *possible* that a succeeding IEFBR14 step would solve this.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Sunday, April 03, 2016 10:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

On Sun, 3 Apr 2016 20:29:09 -0500, Barry Merrill wrote:


Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd.

//FTPUP EXEC PGM=FTP,PARM='(EXIT=4'
//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133
//SYSABEND DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//FTPOUT   DD SYSOUT=*
//INFILE   DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG),
//UNIT=(3390,1),DSNTYPE=LARGE,
//DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144,
//SPACE=(CYL,(500,500),RLSE)
//SYSINDD *
99.99.99.99
USERID   PASSWORDPHRASE
BINARY
GET CICS2.terse +
  'MXGLRG.CICS.UNTERSE' (replace CLOSE QUIT

RLSE is not an attribute that stays with the data set. AFAIK, it only applies 
to the access with that DD statement. If you were to run a step like this:

//COPY   EXEC PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=*
//ALLOC DD  DISP=(NEW,CTLG),DSN=SOME.DATA.SET,
//  SPACE=(TRK,(20,20),RLSE)
//SYSUT1DD  *
record 1
record 2
//SYSUT2DD  DISP=OLD,DSN=SOME.DATA.SET

I think that you would find that the excess space for SOME.DATA.SET is not 
released because the data is not written using the DD statement that has RLSE 
specified.

Likewise, FTP isn't using the INFILE DD statement.

This is only a guess, based upon my understanding of how RLSE works.
I could be wrong.






---
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-04 Thread Vernooij, CP (ITOPT1) - KLM 
RLSE is done during CLOSE of a dataset. IEFBR14 doesn't OPEN/CLOSE datasets.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: 04 April, 2016 13:54
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

Is RLSE ever effective on an input DD (a DD that the program opens for input)?

Oh wait, INFILE is an output DD. Never mind.

In that case Dr. M. could look into the DD:ddname syntax now supported by FTP.

It's also *possible* that a succeeding IEFBR14 step would solve this.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Sunday, April 03, 2016 10:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

On Sun, 3 Apr 2016 20:29:09 -0500, Barry Merrill wrote:

>Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd.
>
>//FTPUP EXEC PGM=FTP,PARM='(EXIT=4'
>//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133
>//SYSABEND DD SYSOUT=*
>//SYSOUT   DD SYSOUT=*
>//FTPOUT   DD SYSOUT=*
>//INFILE   DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG),
>//UNIT=(3390,1),DSNTYPE=LARGE,
>//DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144,
>//SPACE=(CYL,(500,500),RLSE)
>//SYSINDD *
>99.99.99.99
>USERID   PASSWORDPHRASE
>BINARY
>GET CICS2.terse +
>  'MXGLRG.CICS.UNTERSE' (replace CLOSE QUIT

RLSE is not an attribute that stays with the data set. AFAIK, it only applies 
to the access with that DD statement. If you were to run a step like this:

//COPY   EXEC PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=*
//ALLOC DD  DISP=(NEW,CTLG),DSN=SOME.DATA.SET,
//  SPACE=(TRK,(20,20),RLSE)
//SYSUT1DD  *
record 1
record 2
//SYSUT2DD  DISP=OLD,DSN=SOME.DATA.SET

I think that you would find that the excess space for SOME.DATA.SET is not 
released because the data is not written using the DD statement that has RLSE 
specified.

Likewise, FTP isn't using the INFILE DD statement.

This is only a guess, based upon my understanding of how RLSE works. 
I could be wrong.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-04 Thread Charles Mills 
Is RLSE ever effective on an input DD (a DD that the program opens for input)?

Oh wait, INFILE is an output DD. Never mind.

In that case Dr. M. could look into the DD:ddname syntax now supported by FTP.

It's also *possible* that a succeeding IEFBR14 step would solve this.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Sunday, April 03, 2016 10:30 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RLSE does not work with PGM=FTP

On Sun, 3 Apr 2016 20:29:09 -0500, Barry Merrill wrote:

>Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd.
>
>//FTPUP EXEC PGM=FTP,PARM='(EXIT=4'
>//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133
>//SYSABEND DD SYSOUT=*
>//SYSOUT   DD SYSOUT=*
>//FTPOUT   DD SYSOUT=*
>//INFILE   DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG),
>//UNIT=(3390,1),DSNTYPE=LARGE,
>//DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144,
>//SPACE=(CYL,(500,500),RLSE)
>//SYSINDD *
>99.99.99.99
>USERID   PASSWORDPHRASE
>BINARY
>GET CICS2.terse +
>  'MXGLRG.CICS.UNTERSE' (replace CLOSE QUIT

RLSE is not an attribute that stays with the data set. AFAIK, it only applies 
to the access with that DD statement. If you were to run a step like this:

//COPY   EXEC PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=*
//ALLOC DD  DISP=(NEW,CTLG),DSN=SOME.DATA.SET,
//  SPACE=(TRK,(20,20),RLSE)
//SYSUT1DD  *
record 1
record 2
//SYSUT2DD  DISP=OLD,DSN=SOME.DATA.SET

I think that you would find that the excess space for SOME.DATA.SET is not 
released because the data is not written using the DD statement that has RLSE 
specified.

Likewise, FTP isn't using the INFILE DD statement.

This is only a guess, based upon my understanding of how RLSE works. 
I could be wrong.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-03 Thread Paul Gilmartin 
On Sun, 3 Apr 2016 21:11:59 -0500, John McKown wrote:
>
>​Dr. Merrill,
>I know that I'm not in your league. But it looks to me like what you're
>doing is allocating a DSN using JCL, but directing the FTP process to write
>to it using dynamic allocation. So you never really open the DD INFILE or
>do a CLOSE on it. IIRC, RLSE is done by the CLOSE operation. Shouldn't your
>GET look more like:
>
>GET CICS2.terse +
>//DD:INFILE​ (replace
> 
And, perhaps likewise irritating, I've discovered that overriding DCB 
attributes in
the DD statement are ineffective.  FTP will use those in the DSCB regardless.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-03 Thread Tom Marchant 
On Sun, 3 Apr 2016 20:29:09 -0500, Barry Merrill wrote:

>Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd.
>
>//FTPUP EXEC PGM=FTP,PARM='(EXIT=4'
>//SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133
>//SYSABEND DD SYSOUT=*
>//SYSOUT   DD SYSOUT=*
>//FTPOUT   DD SYSOUT=*
>//INFILE   DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG),
>//UNIT=(3390,1),DSNTYPE=LARGE,
>//DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144,
>//SPACE=(CYL,(500,500),RLSE)
>//SYSINDD *
>99.99.99.99
>USERID   PASSWORDPHRASE
>BINARY
>GET CICS2.terse +
>  'MXGLRG.CICS.UNTERSE' (replace
>CLOSE
>QUIT

RLSE is not an attribute that stays with the data set. AFAIK, it only applies 
to the access with that DD statement. If you were to run a step like this:

//COPY   EXEC PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=*
//ALLOC DD  DISP=(NEW,CTLG),DSN=SOME.DATA.SET,
//  SPACE=(TRK,(20,20),RLSE)
//SYSUT1DD  *
record 1
record 2
//SYSUT2DD  DISP=OLD,DSN=SOME.DATA.SET

I think that you would find that the excess space for SOME.DATA.SET is not 
released because the data is not written using the DD statement that has 
RLSE specified.

Likewise, FTP isn't using the INFILE DD statement.

This is only a guess, based upon my understanding of how RLSE works. 
I could be wrong.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RLSE does not work with PGM=FTP

2016-04-03 Thread John McKown 
On Sun, Apr 3, 2016 at 8:29 PM, Barry Merrill  wrote:

> Using IBM FTP CS V2R1, the uploaded INFILE's excess space is not RLSE'd.
>
>
>
> //FTPUP EXEC PGM=FTP,PARM='(EXIT=4'
> //SYSPRINT DD SYSOUT=*,DCB=BLKSIZE=133
> //SYSABEND DD SYSOUT=*
> //SYSOUT   DD SYSOUT=*
> //FTPOUT   DD SYSOUT=*
> //INFILE   DD DSN=MXGLRG.CICS.UNTERSE,DISP=(NEW,CATLG,CATLG),
> //UNIT=(3390,1),DSNTYPE=LARGE,
> //DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=6144,
> //SPACE=(CYL,(500,500),RLSE)
> //SYSINDD *
> 99.99.99.99
> USERID   PASSWORDPHRASE
> BINARY
> GET CICS2.terse +
>   'MXGLRG.CICS.UNTERSE' (replace
> CLOSE
> QUIT
>
>
> I found one reference that CLOSE TYPE=T prevents RLSE, but no reference
>
> if FTP uses TYPE=T.
>

​Dr. Merrill,
I know that I'm not in your league. But it looks to me like what you're
doing is allocating a DSN using JCL, but directing the FTP process to write
to it using dynamic allocation. So you never really open the DD INFILE or
do a CLOSE on it. IIRC, RLSE is done by the CLOSE operation. Shouldn't your
GET look more like:

GET CICS2.terse +
//DD:INFILE​ (replace

ref:
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.halu001/dd_name_support.htm%23dd_name_support?lang=en



> Barry
>
> Herbert W. "Barry" Merrill, PhD
>
> President-Programmer
>
> MXG Software
>
> Merrill Consultants
>
> 10717 Cromwell Drive
>
> Dallas, TX 75229-5112
>
> ba...@mxg.com 
>
> Fax:  214 350 3694 - Still works, received as email
>
> Tel:  214 351 1966 - Unreliable, please use email
>
>

-- 
How many surrealists does it take to screw in a lightbulb? One to hold the
giraffe and one to fill the bathtub with brightly colored power tools.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN