开云体育

Hi!

I'm gathering all the pieces to generate the Starting system using the generating-system zipped JCLs under tk4-, and, while I got the whole picture clear enough to dare giving it a try, I miss a piece.

Reading the description on the zip, I uderstand that both idecams.jcl and usercat.jcl files are VSAM master and user catalogs jobs, that we're advised NOT to be run while generating the staring system under tk4-, right?... if so, further question pop in my misnd: when and where should those jobs be run?... I guess they should be run under a running starter system, but I'm neither sure, nor I understand which volume is SRES17 present on a 3350 for the master catalog... at this point I'm staring to feel I'm missing something beyond what I have at hand.

Could you please give me some clue?

Thank you very much.
Cheers.

Alejandro,

When OS/VS1 and OS/VS2 Rel. 1 first were released, VSAM was not "ready" so
they shipped without it, continuing to use OS/360's SYSCTLG. Then VSAM was
delivered as an ICR - "independent component release" to be added on top of
VS1 or VS2 (SVS). In later releases (refreshes), eventually that VSAM
support was all integrated into the DLIBs. But you still had the option
not to use VSAM initially.

Then, after you have generated your starter system for VS1 or SVS, you can
then generate your ultimate target system with VSAM support included, and
create a Master Catalog on that system. You can do this during the
process of building the target system, or after, by IPLing the target
system, and then running the IDCAMS job to create the new master catalog.
That job will also automatically change the SYSCTLG pointer in
SYS1.NUCLEUS to now point to the new VSAM Master Catalog.

Hope that helps?

Mark

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

Hi!

I'm gathering all the pieces to generate the Starting system using the
generating-system zipped JCLs under tk4-, and, while I got the whole
picture clear enough to dare giving it a try, I miss a piece.

Reading the description on the zip, I uderstand that both idecams.jcl and
usercat.jcl files are VSAM master and user catalogs jobs, that we're
advised NOT to be run while generating the staring system under tk4-,
right?... if so, further question pop in my misnd: when and where should
those jobs be run?... I guess they should be run under a running starter
system, but I'm neither sure, nor I understand which volume is SRES17
present on a 3350 for the master catalog... at this point I'm staring to
feel I'm missing something beyond what I have at hand.

Could you please give me some clue?

Thank you very much.
Cheers.

Hi!

Thank you, that definitely helps :-)
So, essentially, these two jobs are there just for eventual use on the future generated system, and have nothing to do with generating the initial starter system under Tk4-

Cheers!

Hi again.

While I think that I got jobs 1 through 4 cleanly run (cond 0000 AFAIK on all steps), I think something is wrong while running step 5:
I got the last two steps with condition code 0008, and lots of this statements are printed on the job listing:

IEH203I THE SYSCTLG DATA SET IS NOT AVAILABLE OR FORMS A LOOP ... UNUSUAL END

Looking at the documentation, it states that IEH203I code would make the action ignored, so I think the job is not being run properly.

Any clue?

re-running g05 throws JCL error... so, further investigating I'm failing to understand a few things from a high level perspective:
While I can understand that, as explained on file description, that since It is not possible to have TSO on starter sytem because missing help, cmdlib and uads on the tape, and the job has indeed sys1.help and sys1.cmdlib DS allocation commented, I see that sys1.uads is not. And at the same time, I see sys1.logrec DS is commented, but apparently as I interpret it , it is used in the las job step.

Maybe someone could give me a clue on what am I missing regarding g05?

Cheers