I don¡¯t think that the original poster is running MVS 3.8 but OS/390 or newer since has a TCPIP profile dataset.
-trp
What version of MVS or OS/390 or z/OS are you running? Also are you using the ADCD or a copy of a running system?
Laddie Hanus
Sent from whatever device I am using.
toggle quoted message
Show quoted text
On Dec 27, 2020, at 12:50 AM, Mike Schwab <Mike.A.Schwab@...> wrote:
?Turnkey includes the MVS 3.7 starter system on a stand alone volume
for this purpose. And the renames may work under the Turnkey system
and only need the IPL to pick up the new dataset.
On Sat, Dec 26, 2020 at 8:38 PM Pedro Pinheiro <prppedro@...> wrote:
Thanks for the reply, Mike.
Well, if it's the only way, that's what I shall do. I'll probably need to generate another system, though.
Att.,
-trp
On Sat, Dec 26, 2020 at 3:50 PM Mike Schwab <Mike.A.Schwab@...> wrote:
IPL with the starter system.
Create a new name, copy the members over. Rename old dataset. Rename
new dataset.
IPL with normal system.
On Sat, Dec 26, 2020 at 12:36 PM Pedro Pinheiro <prppedro@...> wrote:
Thank you, both of you.
It works well either way. What's more intriguing is that I didn't find it easily in the manuals and Redbooks.
Anyway, there's, now, a second issue. The dataset is accessible, although I can't really write anything to it because it reached its limits (who the heck tights a configuration data set that much during the generation?).
Now I know the most feasible way of doing that is just creating another dataset and moving the files over. But how am I supposed to do that with a system dataset, which is currently open by the system?
About what Rahim said: thank you, but it seems not to be the problem, at all...
On Sat, Dec 26, 2020 at 2:30 PM Rupert Reynolds <rupertreynolds@...> wrote:
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
On Sat., Dec. 26, 2020, 16:33 Joe Monk, <joemonk64@...> wrote:
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
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
