Re: Difficulties with TCP/IP and data sets
|
Good point, but I prefer to leavw the prefix, and simply use apostrophes around dataset names that don't start with it.
sub d(myjob) is easier to type than sub roopy.d.cntl(myjob)
Same with? ex d(myclist) compared with ex roopy.d.clistl(myclist)
call d(myprog) and test d(myprpg) likewise :-)
Roops
TSO PROFILE NOPREFIX.
Then try to access ?your dataset.
Joe
On Sat, Dec 26, 2020 at 10:27 AM Pedro Pinheiro < prppedro@...> wrote: Hi, all
I have a rather dumb question, I recognize. But I've been struggling with it for the past day. There's a data set (CENTER.PARMLIB) in which TCPPROF member is contained. TSO MVSCUST opens this file for me. And I can also access it through DSLIST. Though I can't access it anywhere. Any other ISPF utilities just tells me either the ¡°Data set is not cataloged¡± or (if I specify the volume) ¡°Data set is not found¡±.
That's quite problematic because, on top of all that, system have been abending on me, crying 'bout lack of space in the dataset. But I can't edit CENTER.PARMLIB allocation because all the tools which seems to deal with that can't find the data set. Also, when using the ¡°ALLOC¡± command, it infers the dataset is prefixed the current login, SYSPROG1.
So, is there any way out of this mess?
Thanks,
Att.,
-trp
|
