开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

SVS Rel. 1.7K allocating sysres datasets


 

HI all.
I am trying to generate SVS Rel. 1.7K starter system using TK4-.
I created the necessary DASDs, mounted them under MVS, loaded DLIB from tape to SDLB17 DASD, initialized SGEN17 DASD, and I am trying to allocate the necessary datasets on it.
I am using the job "05-allocate-sysres.jcl", I have added the necessary authorization to the job card.
When I started the job, I got the message:
IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO G05RALC
IEF863I DSN=SYS1.PARMLIB
IEF863I DSN=SYS1.VTAMLIB
*IEF099I JOB G05RALC WAITING FOR DATA SETS

SGEN17 is mounted: 141 3350 O SGEN17 PRIV/RSDNT
and from TSO I can allocate datasets on it.
What am I doing wrong?
Thank you for your answers.
Bruno Novak


 

To answer myself, Job passed when I stopped tso and vtam.


 

Glad you found the fix that works under MVS. It got me thinking, though: running the job under SVS rather than MVS, it works OK running without HASP, but gets ENQ failure for SYS1.PROCLIB with HASP because HOSRDR has SYS1.PROCLIB allocated. This could be a challenge. I'll have to think about it some more.

--
Kevin


 

Hi!

I'm going to try to do so (prepare a starter system from Tk4-) , but I got stuck right from the beginning: I'm missing the control files for the DASDs creation.
So, either I'm missing the point where I have to get additional stuff, or one is supposed to assemble the required control files (which sounds somehow challenging).

Could you give some clue I could follow?

Thank you very much.
Cheers.


 

Use and make needed modifications ctl files from OSVS1 sysgen package.

On Tue, Jul 18, 2023 at 11:52?AM Alejandro olivan Alvarez <
alejandro.olivan.alvarez@...> wrote:

Hi!

I'm going to try to do so (prepare a starter system from Tk4-) , but I got
stuck right from the beginning: I'm missing the control files for the DASDs
creation.
So, either I'm missing the point where I have to get additional stuff, or
one is supposed to assemble the required control files (which sounds
somehow challenging).

Could you give some clue I could follow?

Thank you very much.
Cheers.






 

Use and make needed modifications ctl files from OSVS1 sysgen package.


 

Aha... makes sense!

Will try that, thank you!

Cheers


 

Hi!

How did you stop TSO/VTAM?

I'm not finding how to do that properly/cleanly.
Whatever I do, VTAM never seems to finish to stop and NET, SNASOL,etc keep up.
I bet there's an ellegant way to do that.

I'm thinking on simply manually/cold start tk4- and try to just get jes2 up and running, but now I wonder how did you manage to just stop VTAM/TSO.

Cheers


 

In general, Z NET,QUICK should shut down VTAM and close the ACBs of
applications. In practice, though, it's better to shut down applications
first; thus, P TSO is a good idea (and then replying SIC if you get that
WTOR, then replying U to complete shutdown). I don't know how to stop
SNASOL cleanly, but I would hope P SNASOL would work; if not, you can
always cancel it.

On Fri, Jul 21, 2023 at 8:03?AM Alejandro olivan Alvarez <
alejandro.olivan.alvarez@...> wrote:

Hi!

How did you stop TSO/VTAM?

I'm not finding how to do that properly/cleanly.
Whatever I do, VTAM never seems to finish to stop and NET, SNASOL,etc keep
up.
I bet there's an ellegant way to do that.

I'm thinking on simply manually/cold start tk4- and try to just get jes2
up and running, but now I wonder how did you manage to just stop VTAM/TSO.

Cheers





--
Jay Maynard


 

On Fri, Jul 21, 2023 at 03:02 PM, Alejandro olivan Alvarez wrote:


Hi!

How did you stop TSO/VTAM?

I'm not finding how to do that properly/cleanly.
Whatever I do, VTAM never seems to finish to stop and NET, SNASOL,etc keep up.
I bet there's an ellegant way to do that.

I'm thinking on simply manually/cold start tk4- and try to just get jes2 up
and running, but now I wonder how did you manage to just stop VTAM/TSO.

Cheers
TSO:
P TSO

VTAM:
Z NET,QUICK


 

Hi!

Thank you all.
Y tried initially z net, and then some p tso, p snasol, but I think I just messed it up by not doing it in the right order and omit the ,quick

I'll also be alert expecting the system requiring some replies (SIC first , U afterwards)

Cheers!


 

Hi,

My way to run a SYSGEN of a new system is not allocating
SYS1. datasets, but using another High Level Qualifier.
That is the normal procedure to make a new sysres.

Use in the STAGE1 for example GENERATE INDEX=SYSK.
The system datasets will be allocate with HLQ=SYSK.
In the last job of the STAGE2 output, the SYSK datasets will be
renamed to SYS1.

Cheers,
Rob


 

Hi, Rob,

Thanks for that helpful hint.

The reason Kevin Leonard and I suggested the alternative method using
//JOBCAT or //STEPCAT was because, IIRC, back when OS/VS1 and OS/VS2 Rel. 1
(SVS) were supported, that GENERATE INDEX= stuff just did not seem to work
correctly. So that is why we proposed an alternative to allow the use of
SYS1, without overlaying the real "SYS1." datasets of the generating system.

I should try it again, to see if perhaps that problem was "Fixed" by the
time of the final 1.7L refresh of SVS.

Thanks,

Mark

On Sun, Jul 30, 2023 at 9:45?AM Rob Prins <prin0096@...> wrote:

Hi,

My way to run a SYSGEN of a new system is not allocating
SYS1. datasets, but using another High Level Qualifier.
That is the normal procedure to make a new sysres.

Use in the STAGE1 for example GENERATE INDEX=SYSK.
The system datasets will be allocate with HLQ=SYSK.
In the last job of the STAGE2 output, the SYSK datasets will be
renamed to SYS1.

Cheers,
Rob