Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- H390-OSVS
- Messages
Search
|
ABEND16E BLDL
Hi, all.
I am trying the get RPF running on SVS 1.7L. Most of the modules run fine. I can EDIT, BROWSE, foreground assembly and library functions, However I met an abend16e in BLDL with first operand 0 to find a module in the job pack area or link pack area. According the documentation of SVS BLDL 0 is supported, but will abend. What am I doing wrong? Cheers, Rob |
|
Re: OS/VS1 v1.6.7 SYSGEN issue
Thanks Mark.
I was able to get the OS up and running as v1.6.0 and then install the COBOL, FORTRAN and PL1 compilers that I wanted. Next step is to add an additional WORK DASD. Thanks again, Ron Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<> ________________________________ From: [email protected] <[email protected]> on behalf of Mark Waterbury <mark.s.waterbury@...> Sent: Thursday, February 8, 2024 4:10:29 PM To: [email protected] <[email protected]> Subject: Re: [H390-OSVS] OS/VS1 v1.6.7 SYSGEN issue Ron, What "starter system" are you using? OS/VS1 was meant for the lower end of the 370 family, and starter systems generally had a minimal configuration of devices (tapes, disk drives, etc.) anyway. How many disks are you trying to initialize? You should be able to just create the virtual disks and initialize them "in one go" by using the Hercules "dasdinit" command. Hope that helps, Mark S. Waterbury |
|
Re: OS/VS1 v1.6.7 SYSGEN issue
Ron,
What "starter system" are you using? OS/VS1 was meant for the lower end of the 370 family, and starter systems generally had a minimal configuration of devices (tapes, disk drives, etc.) anyway. How many disks are you trying to initialize? You should be able to just create the virtual disks and initialize them "in one go" by using the Hercules "dasdinit" command. Hope that helps, Mark S. Waterbury |
|
OS/VS1 v1.6.7 SYSGEN issue
I've been trying to perform a SYSGEN for OS/VS1 v1.6.7. However, I can't get past job g04-init-dasd-misc.jcl as it seems there are not enough 3350 DASD devices available in the starter system. I tried a to assign 014b from the WORK61 DASD volume but had the same issue with the PERM73 volume. Has anyone worked through this issue? Or am I doing something wrong? Any insights would be greatly appreciated.
Thank you, Ron Lucas |
|
Re: OS/VS1 Operations
Ron,
toggle quoted message
Show quoted text
Thank you for the detailed cause and solution, this is very helpful. Good luck in your quest to become an OS/VS1 Guru. Hank On Fri, Jan 26, 2024 at 7:00?AM Ron Lucas <lucasrb58@...> wrote:
Hank, |
|
Re: OS/VS1 Operations
Hank,
toggle quoted message
Show quoted text
Certainly.? I performed a SYSGEN of OS/VS1 using Mark Waterbury's v1.6.0 distribution files and Simon Toffler's instructions (available on Moshix github OSVS1 repository).? At the end, when I IPLed the system I wasn't able to run any batch jobs.? I would submit them through the card reader use DEVINIT 00C ... on the Hercules console, but nothing would happen.? I realized none of the I/O devices had been started at IPL time so I used STARTF (sf ,00d and ,00e) to start the punch and printer.? I would start the card reader after the first job was loaded on it since the reader is looking to immediately load a job when started.? Still nothing.? Then I determined that there was no initiator running for any partition on the system.? So, I tried starting one in the P00 partition (the same one used for the SYSGEN) but it kept failing.? I then reviewed the job that loads SYS1.PARMLIB during the SYSGEN (g09-parmlib.jcl) and I noticed that the definition of the P0 initiator/partition was different than the others: ./ ADD NAME=DFN01 P0=(C=*,128K) P1=(C=A,3072K) P2=(C=A,3072K) P3=(C=A,3072K) P4=(C=A,3072K,LAST) So I tried starting an initiator in a different partition (P01) using "S INIT.P1" and it worked.? I was able to submit batch jobs and review the output on the "printer". I suspect this is a very long-winded answer to your request, but it was an interesting exercise for me so I tend to go on about it.? Also, I'm very new to the OS/VS1 system so my use of terminology may not be correct. Ron Lucas On 1/25/2024 4:49 PM, ahp2267 wrote:
Ron, |
|
Re: OS/VS1 Operations
Ron,
toggle quoted message
Show quoted text
Do you mind sharing with everyone what you were missing. Hank On Thu, Jan 25, 2024 at 2:54?PM Ron Lucas <lucasrb58@...> wrote:
Never mind. I figured out what I was missing. |
|
OS/VS1 Operations
I recently completed a SYSGEN of OS/VS1 using Simon Toffler's well written .pdf document. I'm running the OS under Hercules Hyperion 4.6. However I have an issue with submitting batch JCL. When I submit a job using the card reader (devinit 00c myjcllib/myjob.jcl) I don't get a run of the job. I see it sitting on the 00c card reader device on Hercules. However when I start the reader (sf ,00c) and the printer (sf ,00e), I don't see the job execute in the system console or see any output in the printer file (prt00e.txt) but the job is gone from the card reader. I suspect I am missing something in my start up process (possibly an initiator in partition P00?). Has anyone else experienced this?
Thank you, Ron |
|
Re: SVS Rel. 1.7K allocating sysres datasets
Hi, Rob,
toggle quoted message
Show quoted text
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, |
|
Re: SVS Rel. 1.7K allocating sysres datasets
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 |
|
Re: SVS r1.7K generating starter system under tk4-
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 |
|
Re: SVS r1.7K generating starter system under tk4-
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: SVS Rel. 1.7K allocating sysres datasets
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! |
|
Re: SVS r1.7K generating starter system under tk4-
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! |
|
Re: SVS Rel. 1.7K allocating sysres datasets
On Fri, Jul 21, 2023 at 03:02 PM, Alejandro olivan Alvarez wrote:
TSO: P TSO VTAM: Z NET,QUICK |
|
Re: SVS Rel. 1.7K allocating sysres datasets
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!-- Jay Maynard |
Rob Prins
to navigate to use esc to dismiss