On Thu, 27 Apr 2017 19:08:50 -0400, Gord Tomlin wrote:
>
>>> .... Any time Gil succeeds in getting a z/OS
>>> MVS facility to work with z/OS UNIX files, we'll have to update our doc! ;)
>>>
>> Be specific. What qualifies as a "z/OS MVS facility"? IEBGENER works fine.
>> HLASM works fine. Binder works fine. ISPF Edit works fine. Are these,
>> therefore, not to be considered z/OS MVS facilities?
>
>I never said that there were no z/OS MVS facilities that work with z/OS
>UNIX files! I was just (jokingly) expressing that any z/OS MVS facility
>that does not presently work with z/OS UNIX files, and is at some time
>in the future enhanced to work with z/OS UNIX files, may require doc
>changes.
>
Just barely. I imagine that if your doc includes instructions for JCL such as:
//stepname EXEC PGM=AMATERSE,PARM=UNPACK
//SYSUT1 DD DISP=bbb,DSN=your.input.dataset.name
// ...
And AMATERSE UPPACK is suddenly enhanced to allow a UNIX file as SYSUT1,
those instructions remain valid but become a restriction. I wouldn't worry.
I consider it vanishingly unlikely that IBM will someday require that SYSUT1
be a UNIX file.
It should be an easy enhancement for IBM to make. Today this works:
//stepname EXEC PGM=AMATERSE,PARM=UNPACK
//SYSUT1 DD UNIT=SYSALLDA,SPACE=(1,0)
// DD PATHOPTS=ORDONLY,
// PATH='your.input.UNIX.file'
// ...
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
