|
I created some new disks using the Hercules utilities and attached them to addresses 0261, 0262 and 0263 in Hercules.cnf.
After re-IPL, I then used the DASDI macro under id FILE to format the drives
D401 MTS601 VX 2
D402 MTS602 VX 3
D403 MTS603 VX 4
Then, I ran SYS:DSK to attach them to DMGR
ADD MTS601
ADD MTS602
ADD MTS603
No error messages, but when I use the LIST command, DMGR seems not to be able to map them to the devices:
PVN Volume Drive Type Free Total PatA at 10:14:48 on 02-13-23
1 MTS600 on D400 3380 47569 132750 65400
2 MTS601 on where? NoDMGR
3 MTS602 on where? NoDMGR
4 MTS603 on where? NoDMGR
132,747 total pages, 47,569 free pages (39,569 adjusted), 35.8% free.
Adjusted free pages = total free - free POLR - (2000 * #non-POLR volumes) .
Am I missing a step?
Thanks
|
On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote:
Am I missing a step?
I think so. After the ADD, do a DMGR: ADD MTS601 DMGR MTS601 ... If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL. Cheers, Rene FERLAND, Montreal
|
Got it working - Thanks ? There has to be some way in the startup jobs to tell DMGR what volumes to add (actually disks – like D400, D401, etc) . I hope that’s not hardcoded in the system deck (like timezone). ? Been looking around on INIT and STRT and can’t find where DMGR is started. The only thing I see in the startup messages on the console makes me think DMGR is started when PDP mentions it for paging. ? I suppose I can run SYS:DSK from one of the INIT scripts. ? John ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of René Ferland Sent: Monday, February 13, 2023 10:16 To: [email protected]Subject: Re: [H390-MTS] Steps for adding new volumes - I seem to be missing a step (or two) ? On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote: Am I missing a step?
I think so. After the ADD, do a DMGR:
ADD MTS601
DMGR MTS601
...
If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL.
Cheers,
Rene FERLAND, Montreal
|
I realy don't recall how DMGR is started or where it gets a list of disks. I haven't thought about this in around 30 years. I do know that the list of MTS volumes is stored in a table called (I think) DSKTAB in the TABLES assembly and that there is at least one dummy entry at the end of this table where a new volume can be patched in. I'm also pretty sure that's all that is needed to get the new volumes to work with MTS. It shouldn't be hard to patch this table using RAMROD to see if I'm right.
As a minor bit of trivia, this table dates from some time in 1966 back when 6 character names were still the norm (because 6 characters fit in one word on a 704 or derivative).
Mike
toggle quoted message
Show quoted text
On 13 Feb 2023, at 12:49, John Palmer wrote:
Got it working - Thanks
?
There has to be some way in the startup jobs to tell DMGR what volumes to add (actually disks – like D400, D401, etc) . I hope that’s not hardcoded in the system deck (like timezone).
?
Been looking around on INIT and STRT and can’t find where DMGR is started. The only thing I see in the startup messages on the console makes me think DMGR is started when PDP mentions it for paging.
?
I suppose I can run SYS:DSK from one of the INIT scripts.
?
John
?
?
On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote:
Am I missing a step?
I think so. After the ADD, do a DMGR:
ADD MTS601
DMGR MTS601
...
If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL.
Cheers,
Rene FERLAND, Montreal
|
On Dec 5, 2015, at 6:20 PM, Mike Stramba??[H390-MTS] <> wrote:
Ok thx.
What about the *DSK "table" ?
Can it be made permanent ?
Or is the method to just add another script to run at boot to "refresh" it ?
Mike
Take a look here: ??
That message says in part:
MTS will read the volume labels for each online disk at system startup looking for the volume names and public volume numbers that are assembled into DSKTAB and based on what is found the MTS disk volume name and public volume number will be mapped to the appropriate MTS device name; the D6.0 and D6.0A version of DSKTAB expect there to be one MTS disk volume, named MTS600 and it will be public volume 1; ?you can add more disk volumes, but you need to add the new volumes to DSKTAB manually each time you IPL MTS; the *-file job *DSK allows you to work with DSKTAB, they are described in the MTS Operator's Manual.
So if you had a working version of *ASMH, you would reassemble TABLES which includes DSKTAB and add the new volume that way.
But you don’t, so you can run the DSK program (the same program that is run by *DSK) from a *-file job that is run at IPL-time.
Or you could patch DSKTAB in RAMROD and create a new IPLable system.
? ?-Jeff |
|
|
|
On Mon, Feb 13, 2023 at 7:05 PM Mike Alexander < mta@...> wrote:
I realy don't recall how DMGR is started or where it gets a list of disks. I haven't thought about this in around 30 years. I do know that the list of MTS volumes is stored in a table called (I think) DSKTAB in the TABLES assembly and that there is at least one dummy entry at the end of this table where a new volume can be patched in. I'm also pretty sure that's all that is needed to get the new volumes to work with MTS. It shouldn't be hard to patch this table using RAMROD to see if I'm right.
As a minor bit of trivia, this table dates from some time in 1966 back when 6 character names were still the norm (because 6 characters fit in one word on a 704 or derivative).
Mike
On 13 Feb 2023, at 12:49, John Palmer wrote:
Got it working - Thanks
?
There has to be some way in the startup jobs to tell DMGR what volumes to add (actually disks – like D400, D401, etc) . I hope that’s not hardcoded in the system deck (like timezone).
?
Been looking around on INIT and STRT and can’t find where DMGR is started. The only thing I see in the startup messages on the console makes me think DMGR is started when PDP mentions it for paging.
?
I suppose I can run SYS:DSK from one of the INIT scripts.
?
John
?
?
On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote:
Am I missing a step?
I think so. After the ADD, do a DMGR:
ADD MTS601
DMGR MTS601
...
If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL.
Cheers,
Rene FERLAND, Montreal
|
I was able to include this in the INIT scripts. ? Next question: Apparently DMGR only allows 6 volumes. When I try to add #7, it complains that the volume doesn’t exist or no room left in the table. ? Is there a TABLES entry that controls how many volumes you can have? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of Mike Stramba Sent: Monday, February 13, 2023 19:57 To: [email protected]Subject: Re: [H390-MTS] Steps for adding new volumes - I seem to be missing a step (or two) ? On Dec 5, 2015, at 6:20 PM, Mike Stramba??[H390-MTS] <> wrote: ? Ok thx.
What about the *DSK "table" ?
Can it be made permanent ?
Or is the method to just add another script to run at boot to "refresh" it ?
Mike
Take a look here: ?? That message says in part: MTS will read the volume labels for each online disk at system startup looking for the volume names and public volume numbers that are assembled into DSKTAB and based on what is found the MTS disk volume name and public volume number will be mapped to the appropriate MTS device name; the D6.0 and D6.0A version of DSKTAB expect there to be one MTS disk volume, named MTS600 and it will be public volume 1; ?you can add more disk volumes, but you need to add the new volumes to DSKTAB manually each time you IPL MTS; the *-file job *DSK allows you to work with DSKTAB, they are described in the MTS Operator's Manual.
So if you had a working version of *ASMH, you would reassemble TABLES which includes DSKTAB and add the new volume that way. But you don’t, so you can run the DSK program (the same program that is run by *DSK) from a *-file job that is run at IPL-time. Or you could patch DSKTAB in RAMROD and create a new IPLable system. |
|
|
|
? On Mon, Feb 13, 2023 at 7:05 PM Mike Alexander <mta@...> wrote: I realy don't recall how DMGR is started or where it gets a list of disks. I haven't thought about this in around 30 years. I do know that the list of MTS volumes is stored in a table called (I think) DSKTAB in the TABLES assembly and that there is at least one dummy entry at the end of this table where a new volume can be patched in. I'm also pretty sure that's all that is needed to get the new volumes to work with MTS. It shouldn't be hard to patch this table using RAMROD to see if I'm right. As a minor bit of trivia, this table dates from some time in 1966 back when 6 character names were still the norm (because 6 characters fit in one word on a 704 or derivative). Mike On 13 Feb 2023, at 12:49, John Palmer wrote: Got it working - Thanks ? There has to be some way in the startup jobs to tell DMGR what volumes to add (actually disks – like D400, D401, etc) . I hope that’s not hardcoded in the system deck (like timezone). ? Been looking around on INIT and STRT and can’t find where DMGR is started. The only thing I see in the startup messages on the console makes me think DMGR is started when PDP mentions it for paging. ? I suppose I can run SYS:DSK from one of the INIT scripts. ? John ? ? On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote: Am I missing a step?
I think so. After the ADD, do a DMGR:
ADD MTS601
DMGR MTS601
...
If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL.
Cheers,
Rene FERLAND, Montreal
|
FYI: Figured this out. TABLES has 6 slots defined and apparently that’s the max you can add either by patching to have them load automatically at IPL time or even dynamically with SYS:DSK. ? So, without a recompile, you can’t have more than 6, period. ? ?
toggle quoted message
Show quoted text
From: [email protected] < [email protected]> On Behalf Of John Palmer Sent: Tuesday, February 21, 2023 06:53 To: [email protected]Subject: Re: [H390-MTS] Steps for adding new volumes - I seem to be missing a step (or two) ? I was able to include this in the INIT scripts. ? Next question: Apparently DMGR only allows 6 volumes. When I try to add #7, it complains that the volume doesn’t exist or no room left in the table. ? Is there a TABLES entry that controls how many volumes you can have? ? ? On Dec 5, 2015, at 6:20 PM, Mike Stramba??[H390-MTS] <> wrote: ? Ok thx.
What about the *DSK "table" ?
Can it be made permanent ?
Or is the method to just add another script to run at boot to "refresh" it ?
Mike
Take a look here: ?? That message says in part: MTS will read the volume labels for each online disk at system startup looking for the volume names and public volume numbers that are assembled into DSKTAB and based on what is found the MTS disk volume name and public volume number will be mapped to the appropriate MTS device name; the D6.0 and D6.0A version of DSKTAB expect there to be one MTS disk volume, named MTS600 and it will be public volume 1; ?you can add more disk volumes, but you need to add the new volumes to DSKTAB manually each time you IPL MTS; the *-file job *DSK allows you to work with DSKTAB, they are described in the MTS Operator's Manual.
So if you had a working version of *ASMH, you would reassemble TABLES which includes DSKTAB and add the new volume that way. But you don’t, so you can run the DSK program (the same program that is run by *DSK) from a *-file job that is run at IPL-time. Or you could patch DSKTAB in RAMROD and create a new IPLable system. |
|
|
|
? On Mon, Feb 13, 2023 at 7:05 PM Mike Alexander <mta@...> wrote: I realy don't recall how DMGR is started or where it gets a list of disks. I haven't thought about this in around 30 years. I do know that the list of MTS volumes is stored in a table called (I think) DSKTAB in the TABLES assembly and that there is at least one dummy entry at the end of this table where a new volume can be patched in. I'm also pretty sure that's all that is needed to get the new volumes to work with MTS. It shouldn't be hard to patch this table using RAMROD to see if I'm right. As a minor bit of trivia, this table dates from some time in 1966 back when 6 character names were still the norm (because 6 characters fit in one word on a 704 or derivative). Mike On 13 Feb 2023, at 12:49, John Palmer wrote: Got it working - Thanks ? There has to be some way in the startup jobs to tell DMGR what volumes to add (actually disks – like D400, D401, etc) . I hope that’s not hardcoded in the system deck (like timezone). ? Been looking around on INIT and STRT and can’t find where DMGR is started. The only thing I see in the startup messages on the console makes me think DMGR is started when PDP mentions it for paging. ? I suppose I can run SYS:DSK from one of the INIT scripts. ? John ? ? On Mon, Feb 13, 2023 at 07:16 AM, John Palmer wrote: Am I missing a step?
I think so. After the ADD, do a DMGR:
ADD MTS601
DMGR MTS601
...
If I remember well, the additions are "temporary", you will need to run SYS:DSK again to (re-) add your disks after each IPL.
Cheers,
Rene FERLAND, Montreal
|
René Ferland