Hi
Why don't you teach you group to Unix ? ;-)
If you don't want to keep this project for you, I would consider the 44
byte long MVS dataset names.
I always wanted to have an option, to assign long , descriptive alias
names to MVS datasets.
Maybe the "jol" can do this or the "xjcl".
On 7/19/2011 3:35 PM, John McKown wrote:
I'm working on a project which involves "converting" a lot of VSAM
files. So far, I've restricted myself to using PDSes and REXX. Everybody
in my group (mainframe sysprogs) understands these. But, for my own
convenience, I'd like to use UNIX files. Why? Because I can create
really long file names, such as: export-jcl.<vsam_dsn>,
import-jcl.<vsam_dsn>, define-jcl.<vsam_dsn>, and so forth. But nobody
else in my group really "digs" UNIX stuff and none of them, other than
myself, actually likes it.
So, should I restrict myself to only using generally understandable
stuff. Or, since this project is not production (basically do the
conversion then ignore it), should I just do it the way that is easiest
for me? The problem with this is that there are a large number of files
to convert and it will take quite a while. So using UNIX basically means
it is my baby entirely.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
