¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. H390-DOSVS
  2. Topics

DOS/360: cancelled during install...

 

I'm working through Steven Orso's excellent DOS/360 installation page, just for grins. Unfortunately, I ran into a problem: the migrate03 job blew up with a "library full" cancel during copying the COBOL relocatable library:

3M53I? RELOCATABLE LIBRARY IS FULL

Is this a known issue, or did I screw up somewhere? Or is there a better place to ask?
 

Jay Maynard wrote:

I'm working through Steven Orso's excellent DOS/360 installation
page, just for grins. Unfortunately, I ran into a problem: the
migrate03 job blew up with a "library full" cancel during copying
the COBOL relocatable library:

3M53I RELOCATABLE LIBRARY IS FULL

Is this a known issue, or did I screw up somewhere? Or is there a
better place to ask?
Hi Jay! No, AFAIK this is the correct place to ask such questions. In fact, AFAIK it's the *only* place to ask such questions!

Do you have the URL for this web page of Steve's? I don't remember ever seeing it. I'd like to give his procedure a try myself to see whether the same problem occurs for me too.

Also, I take it you DO know how to deal with ("recover" from) such a problem since you didn't ask, that all you're really interested in is whether the error should be considered expected or not, yes?

I can't tell you how good it is to see you active in Hercules again! :)
--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...
 

Thanks!

And no, I'm not a DOS person at all, so I don't know how to recover from it. I assume the answer is to reallocate the library, but I'm not entirely sure how.

The page is at? .

My eventual goal is to get every system possible running under VM/370 Community Edition. That includes both 360 and 370 OSes, VS and non-. Kind of a Swiss Army knife distribution.

On Tue, Aug 10, 2021 at 10:28 AM Fish Fish <david.b.trout@...> wrote:
Jay Maynard wrote:

> I'm working through Steven Orso's excellent DOS/360 installation
> page, just for grins. Unfortunately, I ran into a problem: the
> migrate03 job blew up with a "library full" cancel during copying
> the COBOL relocatable library:
>
> 3M53I? RELOCATABLE LIBRARY IS FULL
>
> Is this a known issue, or did I screw up somewhere? Or is there a
> better place to ask?

Hi Jay! No, AFAIK this is the correct place to ask such questions. In fact, AFAIK it's the *only* place to ask such questions!

Do you have the URL for this web page of Steve's? I don't remember ever seeing it. I'd like to give his procedure a try myself to see whether the same problem occurs for me too.

Also, I take it you DO know how to deal with ("recover" from) such a problem since you didn't ask, that all you're really interested in is whether the error should be considered expected or not, yes?

I can't tell you how good it is to see you active in Hercules again! :)
--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...











--
Jay Maynard
 

Fish,

Jay Moseley points to Steve Orso's instructions on his

Chris
--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Tue, 10 Aug 2021 08:27:56 -0700
"Fish Fish" <david.b.trout@...> wrote:
Jay Maynard wrote:

I'm working through Steven Orso's excellent DOS/360 installation
page, just for grins. Unfortunately, I ran into a problem: the
migrate03 job blew up with a "library full" cancel during copying
the COBOL relocatable library:

3M53I RELOCATABLE LIBRARY IS FULL

Is this a known issue, or did I screw up somewhere? Or is there a
better place to ask?
Hi Jay! No, AFAIK this is the correct place to ask such questions. In fact, AFAIK it's the *only* place to ask such questions!

Do you have the URL for this web page of Steve's? I don't remember ever seeing it. I'd like to give his procedure a try myself to see whether the same problem occurs for me too.

Also, I take it you DO know how to deal with ("recover" from) such a problem since you didn't ask, that all you're really interested in is whether the error should be considered expected or not, yes?

I can't tell you how good it is to see you active in Hercules again! :)
--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...
 

Jay,

It is a long time ago, but I recall hitting this. My memory about how I
got round this (if I did) is failing me.

Chris
--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Mon, 09 Aug 2021 18:12:01 -0700
"Jay Maynard" <jaymaynard@...> wrote:
I'm working through Steven Orso's excellent DOS/360 installation page, just for grins. Unfortunately, I ran into a problem: the migrate03 job blew up with a "library full" cancel during copying the COBOL relocatable library:

3M53I? RELOCATABLE LIBRARY IS FULL

Is this a known issue, or did I screw up somewhere? Or is there a better place to ask?
 

¿ªÔÆÌåÓý

Hi Jay,
I have just run the DOS 26 installation from scatch, as per the web site, up to and including the migrate03,
and it completed without the error of filling the relo lib.
One thought is that DOS libs can't reuse space immediately when members are deleted or replaced.
To make the deleted space available you need to either condense the lib with maint,
or maybe copy and reload it from empty.
The installation procedure is set up to load up from newly created libraries,
so if you had any hiccups or reruns, you may have been copying/replacing into libs with space already used.
Eddy Balem
 

Hi Jay,

First, thanks for your MVT tutorial.? Good fun, learned a lot.??

Can you upload the printout from MIGRATE03 and the telnet console log if you have it (no need to recreate if you don't)?? However one does that here.??

The libraries are sized such that they should be large enough for the content loaded in MIGRATE03.? Eddie is correct that MAINT can be used to condense the library.? SYSGEN90 includes this step to reclaim space consumed by SYSGEN activities.? But a "CONDS CL,RL,SL" should not be needed in MIGRATE03.??

Best Regards,
Steve Orso
 

Sure! I uploaded the entire migrate-3 printer output to the files area, as?/g/H390-DOSVS/files/migrate-3-loadlibs.txt .

And you're quite welcome for the MVT doc. I'm glad it's still teaching people.

On Wed, Aug 11, 2021 at 6:09 PM <stephen.orso@...> wrote:
Hi Jay,

First, thanks for your MVT tutorial.? Good fun, learned a lot.??

Can you upload the printout from MIGRATE03 and the telnet console log if you have it (no need to recreate if you don't)?? However one does that here.??

The libraries are sized such that they should be large enough for the content loaded in MIGRATE03.? Eddie is correct that MAINT can be used to condense the library.? SYSGEN90 includes this step to reclaim space consumed by SYSGEN activities.? But a "CONDS CL,RL,SL" should not be needed in MIGRATE03.??

Best Regards,
Steve Orso



--
Jay Maynard
 

Looking at your migrate print it looks like it really filled the relocation lib, mine was only just over half full after the whole job. I was using a recent sdl hyperion build under Linux mint. I would look at whether the migrate tape somehow had spurious extra records being catalogued. Under Dos it should be unblocked card images.
Eddy balem
 

I uploaded a reference listing from 2016 that shows what things look like when things work:?/g/H390-DOSVS/files/migrate-3-loadlibs-ref.txt

Looking at uploaded listing of the failure, it would appear to be a tape positioning issue, although I do not understand why it occurred. It will take a bit of time for a longer response.??
 

I reran?it on a different machine, and the MIGRATE jobs went through just?fine. I had some trouble getting the newly built 190 pack IPLd the first time around, and it's entirely possible that things were left with the 280 tape in the wrong position.

I'm going through the rest of it now. I don't expect any trouble, but we'll see.

On Thu, Aug 12, 2021 at 5:32 PM <stephen.orso@...> wrote:
I uploaded a reference listing from 2016 that shows what things look like when things work:?/g/H390-DOSVS/files/migrate-3-loadlibs-ref.txt

Looking at uploaded listing of the failure, it would appear to be a tape positioning issue, although I do not understand why it occurred. It will take a bit of time for a longer response.??



--
Jay Maynard
 

I'm glad things are working better, Let me know how you make out, and in particular what you need to do to run it under VM/370.

I would loved to have used disk for the files created/consumed by MIGRATE, but DOS does not allow blocked files of cards for input to utilities.? Would have required lots of disk for unblocked 80/81-byte records.??
 

On Fri, Aug 13, 2021 at 03:20 PM, <stephen.orso@...> wrote:
[...] and in particular what you need to do to run it under VM/370.
Have you run your DOS/360 under VM/370? It should not be very hard. But the one problem I see is handshaking (automatic close of spool print/punch files), probably not implemented on DOS/360. The OS has to be patched for that. George Shedlock did it for DOS/VS.

Cheers,

Rene FERLAND, Montreal
 

The one issue I see is that you can't really automate anything with CMS EXECs, since CMS assumes the A-disk is at 191, and the supplied stuff assumes SPOOL1 is there. I would assume that POWER could be patched to do the handshaking, if the source code where that would be needed is present, or the hook locations are known.


On Fri, Aug 13, 2021 at 11:43 PM Ren¨¦ Ferland <ferland.rene@...> wrote:
On Fri, Aug 13, 2021 at 03:20 PM, <stephen.orso@...> wrote:
[...] and in particular what you need to do to run it under VM/370.
Have you run your DOS/360 under VM/370? It should not be very hard. But the one problem I see is handshaking (automatic close of spool print/punch files), probably not implemented on DOS/360. The OS has to be patched for that. George Shedlock did it for DOS/VS.

Cheers,

Rene FERLAND, Montreal



--
Jay Maynard
 

Hoping there is someone who will be able to help with the handshaking as this OS is my primary interest for running under VM/370.

Thanks again?Ren¨¦ for getting me running!

Roger
 

Ran through the verify steps. Everything ran fine, though I did have to change the ASSGNs in veraso04.jcl for the printer to X'02E'.
The original versions got?1A14D ?CONFLICTING I/O ASSIGNMENT messages.

Looks like it's good, now. And for initial VM use, we can always just dedicate?a real 1403 to it...

On Sat, Aug 14, 2021 at 12:21 PM xraydelta1 <roger.mccarty@...> wrote:
Hoping there is someone who will be able to help with the handshaking as this OS is my primary interest for running under VM/370.

Thanks again?Ren¨¦ for getting me running!

Roger



--
Jay Maynard
 

Thanks for reporting the ASSGN statement error in verasm04.jcl.? That's been there a while.? The archive has been updated (one line in one file) and future downloads will include the correction.??

I will start a separate thread for DOS/360 on VM (on Hercules).? A "real" 1403 is not a bad approach.??

I hadn't considered the impact of using device range 190-193 for the 2314's in a CMS automation environment.? There's no significance to the device addresses.? 160-163 would work just as well, and it's not a complicated change.? Just very very (very) tedious.??
 

Think you'll find two lurking X'00e's in verasm04.jcl...I did, at least.

And yeah, I thought about making that change to another range myself, but decided to defer it until others had had a chance to weigh in. VM/370 CE has 16x genned as 3340s, but that's not a big deal, just use the directory entry to put the DASD at the addresses you want.

On Sun, Aug 15, 2021 at 3:45 PM Steve Orso <stephen.orso@...> wrote:
Thanks for reporting the ASSGN statement error in verasm04.jcl.? That's been there a while.? The archive has been updated (one line in one file) and future downloads will include the correction.??

I will start a separate thread for DOS/360 on VM (on Hercules).? A "real" 1403 is not a bad approach.??

I hadn't considered the impact of using device range 190-193 for the 2314's in a CMS automation environment.? There's no significance to the device addresses.? 160-163 would work just as well, and it's not a complicated change.? Just very very (very) tedious.??



--
Jay Maynard
 

00e->02e: Got 'em both in the above update.? Thanks!

Agreed re additional feedback on device addresses, hence the separate topic for DOS/360 under VM.? Spooling deserves discussion.??

1 - 19 of 19