[hercules-390] Can't IPL During Install of Hercules 3.07

[[e-mail] [hercules-390]]

Trying to install DOS 360. Have initialised the 2311 and 2314 drives and tapes. Stuck while trying load images at IPL 132 which fails for:

S/370 mode IPL failed: CSW status=0E00 Sense=000800C8 0000

Does this error suggest anything about the cause?

[Mike Stramba [e-mail] [hercules-390]]

>S/370 mode IPL failed:

Check your hercules.cnf (or otherwise named config file) for the ARCHMODE.

It might be set to ESA/390 as default, needs to be s/370.

I'm going more off the "S/370 mode IPL failed" message.

The real experts here can probably decipher the CSW status=0E00
Sense=000800C8 0000 ... without even looking it up ;)

Mike


On 11/17/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Trying to install DOS 360. Have initialised the 2311 and 2314 drives and
> tapes. Stuck while trying load images at IPL 132 which fails for:
>
> S/370 mode IPL failed: CSW status=0E00 Sense=000800C8 0000
>
> Does this error suggest anything about the cause?

[Mike Stramba [e-mail] [hercules-390]]

Also check the MAINSIZE

Prob not more than 4 for dos360.

Mike

On 11/17/16, Mike Stramba <***@gmail.com> wrote:
>>S/370 mode IPL failed:
>
> Check your hercules.cnf (or otherwise named config file) for the ARCHMODE.
>
> It might be set to ESA/390 as default, needs to be s/370.
>
> I'm going more off the "S/370 mode IPL failed" message.
>
> The real experts here can probably decipher the CSW status=0E00
> Sense=000800C8 0000 ... without even looking it up ;)
>
> Mike
>
>
> On 11/17/16, ***@mac.com [hercules-390]
> <hercules-***@yahoogroups.com> wrote:
>> Trying to install DOS 360. Have initialised the 2311 and 2314 drives and
>> tapes. Stuck while trying load images at IPL 132 which fails for:
>>
>> S/370 mode IPL failed: CSW status=0E00 Sense=000800C8 0000
>>
>> Does this error suggest anything about the cause?
>

[[e-mail] [hercules-390]]

MAINSIZE was/is set to 2.

Thanks.



From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Thursday, November 17, 2016 9:06 PM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Can't IPL During Install of Hercules 3.07

 
Also check the MAINSIZE

Prob not more than 4 for dos360.

Mike

On 11/17/16, Mike Stramba <***@gmail.com> wrote:
>>S/370 mode IPL failed:
>
> Check your hercules.cnf (or otherwise named config file) for the ARCHMODE.
>
> It might be set to ESA/390 as default, needs to be s/370.
>
> I'm going more off the "S/370 mode IPL failed" message.
>
> The real experts here can probably decipher the CSW status=0E00
> Sense=000800C8 0000 ... without even looking it up ;)
>
> Mike
>
>
> On 11/17/16, ***@mac.com [hercules-390]
> <hercules-***@yahoogroups.com> wrote:
>> Trying to install DOS 360. Have initialised the 2311 and 2314 drives and
>> tapes. Stuck while trying load images at IPL 132 which fails for:
>>
>> S/370 mode IPL failed: CSW status=0E00 Sense=000800C8 0000
>>
>> Does this error suggest anything about the cause?
>




[Non-text portions of this message have been removed]

['Mark L. Gaubatz' [e-mail] [hercules-390]]

CSW :: Channel End + Device End + Unit Check

Sense :: Most likely console. If DASD, the Sense bytes make no sense for
IPL -- No Record Found + Busy + Online + Pack Change


On 11/17/2016 07:53 PM, Mike Stramba ***@gmail.com
[hercules-390] wrote:
>
> The real experts here can probably decipher the CSW status=0E00
> Sense=000800C8 0000 ... without even looking it up ;)
>

[Martin Truebner [e-mail] [hercules-390]]

If the system reacts with a CSW it is because some I/O failed in some
way (I need the green card to decipher the exact meaning)-

check that the IPL device and the console at 009 are of the specified
type.

Martin TrÃŒbner; everything around "PoOps of z/arch"

[[e-mail] [hercules-390]]

Hhmm, console line reads:
001F 1052 noprompt

I will change to 0009

0132 is a DASD 2311 at this point. The 2311s have not yet been migrated to 2314s.

I will try using 0130 and 0131, just in case. All three are 2311s.

Thanks.



From: Martin Truebner ***@pi-sysprog.de [hercules-390]
Sent: Friday, November 18, 2016 12:47 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Can't IPL During Install of Hercules 3.07

 
If the system reacts with a CSW it is because some I/O failed in some
way (I need the green card to decipher the exact meaning)-

check that the IPL device and the console at 009 are of the specified
type.

Martin TrÃŒbner; everything around "PoOps of z/arch"




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

- - - In hercules-***@yahoogroups.com, <***@...> wrote:
> Trying to install DOS 360. Have initialised the 2311 and 2314
>drives and tapes.

Which utility did you use to create the disk images?
dasdinit or dasdload?

Did you specify dasd init device types, hercules device
definitions, and the operating system genned device
addresses and types?
If 132 is a 2311, it must match what the dasd init was told,
what is in your hercules configuration file, what the restore
program defaulted to or was rold, and what was genned at
that address.

If dasdinit was used to create the disk, then you need
another utility to init the disks. IBCDASDI or ICKSADSF.

How did you initialize tapes and why?

> Stuck while trying load images at IPL 132 which fails for:

Which utility did you use to load ( tape ) images from the
newly cleared tapes to the empty disk at 132 ?

If 132 was empty but about to be loaded, trying to
IPL 132 might not work.

> S/370 mode IPL failed: CSW status=0E00 Sense=000800C8 0000
> Does this error suggest anything about the cause?

What is your console address and device type?

001F 1052-c
or
0009 1052-c
or both?
If you forget the "-c" then you must telnet to the address before
each attempted IPL.

Reviewing whatever instructions that came with the system you
downloaded might help? Might not?

[[e-mail] [hercules-390]]

Hi '***@mac.com'

The message is generated by Hercules when the Read IPL command fails. Read IPL from disk expects to find a 24-byte record at Cyl 0 Head 0 record 1, with a command chain to whatever got read in, which should be at least one more CCW.


Sense=0008 corresponds to no record found on a disk device. For tape, it means load point...And no, I don't have them memorized. :-)


Were you IPLing the tape to do the restore, or were you IPLing 132 following completion of the restore? Based on the sense, I suspect you were IPLing 132.


If you were IPLing the tape, then the tape is likely not positioned correctly for IPL, but that does not square up to Load Point.


If you were IPLing the disk following restore, then the sense information makes sense (sorry), and the restore likely did not restore the system residence volume successfully. DOS/360 stand-alone utilities were not very robust, nor did they provide detailed messages upon failure. And it is hard to find documentation describing the cryptic codes offered when an error appears.


But first, a question: which set of instructions are you following? I know of three: mine and the two that were the basis for mine. All have this in common:



Use dasdinit to create unformatted 2311 volumes
IPL distribution tape one, initialize volume 130
rewind and IPL distribution tape one, initialize 131.
Do not rewind, IPL distribution tape one, restore 130 and 131.
IPL distribution tape two, initialize volume 132
Do not rewind, IPL distribution tape one, restore 132 (sysres and private libraries).



A layout of the distribution tapes can be found here:

https://sites.google.com/site/dos360install/dosdistrib/dostapes https://sites.google.com/site/dos360install/dosdistrib/dostapes

Console output from the initialize and restore to 132 looks like this:


CONTROL CARD ANALYSIS AND LABEL CHECKING
UTILITY MODIFIER CARD
// UID IR,C1
SURFACE ANALYSIS AND HA-R0 GENERATION
SYSOPT
LAB CYL CREATION
SYSOPT
// VTOC STRTADR=(0199000),EXTENT=(10)
VOL1RES11C
EOJ
DISTRIBUTION PROGRAM
RESTORE FUNCTION
* DOS SYSTEM/360 RELEASE 26.2 SYSRES 2311 VOLUME 3
DOS.SYSRES.FILE.VOLUME.3
THIS FILE FOR SYS000
4307A
22
DOS.SYSRES.FILE.VOLUME.3
000752 RECORDS RESTORED FOR ABOVE FILE
3007
DOS.SYSRLB.FILE.VOLUME.3
THIS FILE FOR SYS000
4307A
22
DOS.SYSRLB.FILE.VOLUME.3
003320 RECORDS RESTORED FOR ABOVE FILE
3007
DOS.SYSSLB.FILE.VOLUME.3
THIS FILE FOR SYS000
4307A
22
DOS.SYSSLB.FILE.VOLUME.3
014499 RECORDS RESTORED FOR ABOVE FILE
3007
END OF JOB
3008
0281
2E0F
4022A


Record counts must match. The volume name, RES11C in the above example, may be different depending on the instructions you're using and is not critical at this early point in the process.


But the best next step is to let us know which instructions you are following and to confirm that you were IPLing the tape or the disk.


Best Regards,
Steve Orso

[[e-mail] [hercules-390]]

Hi, Steve. Thanks for following up - much appreciated!


Yes, I'm following your instructions. And, yes, I was trying to IPL from the 2311 on 132.


I think the first thing to fall back to is to delete everything and start over from the beginning. I'll report back on how it goes.


Couple questions. First, I was using the Jason GUI - could that have anything to do with things? Second, I have attempted to see the console output both using Jason as well as using tn3270. No dice. How would you recommend connecting to see console output?


Again, many thanks.


Michael

[Mike Stramba [e-mail] [hercules-390]]

On 11/20/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Couple questions. First, I was using the Jason GUI - could that have
> anything to do with things?

Uh, yeah, that's a rather important detail you left out :/

You should just try "bare" Hercules first to eliminate as many
variables as possible.

I tried running Jason awhile ago, and couldn't get it to work, a brief
look through my emails and it had something to do with not being able
to find dasd.

I emailed the author but never got a reply, so I dropped using it.

I'll try firing it up again, and/or try to find what error messages I
was getting.

And ... do you have specific interest in dos360, rather than dos34?

The latter is much more "polished" and easier to use.

Though, no harm in running both, ... or just '360 if that's your interest.

Mike

[[e-mail] [hercules-390]]

Hi! Please see my reply with screenshot. Yes, I really do want to work with Hercules 3.07 for DOS.

Thanks!

Sent from my Windows 10 phone

From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Monday, November 21, 2016 2:04 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
On 11/20/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Couple questions. First, I was using the Jason GUI - could that have
> anything to do with things?

Uh, yeah, that's a rather important detail you left out :/

You should just try "bare" Hercules first to eliminate as many
variables as possible.

I tried running Jason awhile ago, and couldn't get it to work, a brief
look through my emails and it had something to do with not being able
to find dasd.

I emailed the author but never got a reply, so I dropped using it.

I'll try firing it up again, and/or try to find what error messages I
was getting.

And ... do you have specific interest in dos360, rather than dos34?

The latter is much more "polished" and easier to use.

Though, no harm in running both, ... or just '360 if that's your interest.

Mike




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Hi Michael.

I don't know the answer to any of your questions,
but would you mind sharing why you want to use
that exact version of Hercules (3.07) and that
exact version of DOS/VS (DOS/360)?


BFN. Paul.





---In hercules-***@yahoogroups.com, <***@...> wrote :

Hi! Please see my reply with screenshot. Yes, I really do want to work with Hercules 3.07 for DOS.

Thanks!

Sent from my Windows 10 phone

From: Mike Stramba ***@... mailto:***@... [hercules-390]
Sent: Monday, November 21, 2016 2:04 AM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


On 11/20/16, ***@... mailto:***@... [hercules-390]
<hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com> wrote:
>
> Couple questions. First, I was using the Jason GUI - could that have
> anything to do with things?

Uh, yeah, that's a rather important detail you left out :/

You should just try "bare" Hercules first to eliminate as many
variables as possible.

I tried running Jason awhile ago, and couldn't get it to work, a brief
look through my emails and it had something to do with not being able
to find dasd.

I emailed the author but never got a reply, so I dropped using it.

I'll try firing it up again, and/or try to find what error messages I
was getting.

And ... do you have specific interest in dos360, rather than dos34?

The latter is much more "polished" and easier to use.

Though, no harm in running both, ... or just '360 if that's your interest.

Mike




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Paul, It’s probably not a good reason, but that’s what I cut my teeth on back in my first year as a COBOL programmer. I’ve been hoping to have a little fun trying out some COBOL coding again.

If a little newer version would be easier to get set up, that’s cool. But the instructions looked so easy - didn’t realize it was such a pesky process.

Sent from my Windows 10 phone

From: ***@yahoo.com.au [hercules-390]
Sent: Monday, December 12, 2016 5:56 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Michael.

I don't know the answer to any of your questions,
but would you mind sharing why you want to use
that exact version of Hercules (3.07) and that
exact version of DOS/VS (DOS/360)?

BFN. Paul.




---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi! Please see my reply with screenshot. Yes, I really do want to work with Hercules 3.07 for DOS.

Thanks!

Sent from my Windows 10 phone

From: Mike Stramba ***@... [hercules-390]
Sent: Monday, November 21, 2016 2:04 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
On 11/20/16, ***@... [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Couple questions. First, I was using the Jason GUI - could that have
> anything to do with things?


Uh, yeah, that's a rather important detail you left out :/

You should just try "bare" Hercules first to eliminate as many
variables as possible.

I tried running Jason awhile ago, and couldn't get it to work, a brief
look through my emails and it had something to do with not being able
to find dasd.

I emailed the author but never got a reply, so I dropped using it.

I'll try firing it up again, and/or try to find what error messages I
was getting.

And ... do you have specific interest in dos360, rather than dos34?

The latter is much more "polished" and easier to use.

Though, no harm in running both, ... or just '360 if that's your interest.

Mike




[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Ok, fair enough.

But of course all the Cobol code you
wrote back then should continue to
work on later versions of DOS.

Maybe it's not relevant to you, but
with VSE/380 you can even write
31-bit programs (in assembler and
C, not DOS-supplied Cobol).

In fact on VSE/380 with the latest beta
Hercules/380 you should even be able
to write 64-bit programs (both 64-bit
registers and 64-bit addressing).

BFN. Paul.




---In hercules-***@yahoogroups.com, <***@...> wrote :

Paul, It’s probably not a good reason, but that’s what I cut my teeth on back in my first year as a COBOL programmer. I’ve been hoping to have a little fun trying out some COBOL coding again.

If a little newer version would be easier to get set up, that’s cool. But the instructions looked so easy - didn’t realize it was such a pesky process.

Sent from my Windows 10 phone

From: ***@... mailto:***@... [hercules-390]
Sent: Monday, December 12, 2016 5:56 PM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Hi Michael.

I don't know the answer to any of your questions,
but would you mind sharing why you want to use
that exact version of Hercules (3.07) and that
exact version of DOS/VS (DOS/360)?

BFN. Paul.




---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@...> wrote :
Hi! Please see my reply with screenshot. Yes, I really do want to work with Hercules 3.07 for DOS.

Thanks!

Sent from my Windows 10 phone

From: Mike Stramba ***@... [hercules-390]
Sent: Monday, November 21, 2016 2:04 AM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


On 11/20/16, ***@... [hercules-390]
<hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com> wrote:
>
> Couple questions. First, I was using the Jason GUI - could that have
> anything to do with things?


Uh, yeah, that's a rather important detail you left out :/

You should just try "bare" Hercules first to eliminate as many
variables as possible.

I tried running Jason awhile ago, and couldn't get it to work, a brief
look through my emails and it had something to do with not being able
to find dasd.

I emailed the author but never got a reply, so I dropped using it.

I'll try firing it up again, and/or try to find what error messages I
was getting.

And ... do you have specific interest in dos360, rather than dos34?

The latter is much more "polished" and easier to use.

Though, no harm in running both, ... or just '360 if that's your interest.

Mike




[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Hi Michael:

OK, then it would appear that you are on step MIGRATE01, the first IPL of the restored distribution system, and that you have restored all tapes. But based on what you say about Jason and tn3270, you have not seen much to let you know if the restores worked.


I am not familiar with the Jason GUI...do you have a link?


DOS/360 did not have any support for 3270 devices as an operator console, so tn3270 will not help much either.


And Hercules 3.07 did not support a wide range of telnet clients. In particular, PuTTY will not connect. I used a Windows NT Telnet client, which will not work so well on a Linux system if that's what you are using.


I suggest you repeat the process using the Hercules integrated console. The statements to do this are commented in the CNF files. Just uncomment them, comment the original console statements, and prefix reponses to the restore program with a \ (backwards slash).


That should give you console output to let you (and us) see how the restores are doing. And if they fail, we can see logs that will help diagnose this.



I agree with Mike that DOS/VS release 34 is more polished--it was in real life too--but I had a great time messing around with DOS/360--again, in real life too. In the age of iPhones and GUI's, it's interesting to see what things were like 50 years ago.


Best Regards,
Steve Orso


---In hercules-***@yahoogroups.com, <***@...> wrote :

Hi, Steve. Thanks for following up - much appreciated!


Yes, I'm following your instructions. And, yes, I was trying to IPL from the 2311 on 132.


I think the first thing to fall back to is to delete everything and start over from the beginning. I'll report back on how it goes.


Couple questions. First, I was using the Jason GUI - could that have anything to do with things? Second, I have attempted to see the console output both using Jason as well as using tn3270. No dice. How would you recommend connecting to see console output?


Again, many thanks.


Michael

[[e-mail] [hercules-390]]

Ok, I’ve started over from scratch with the DOS/360 install process. I’ve gotten up to the step titled “DISTRIB03 restore distribution tape one to RES11A and RES11B”.

DISTRIB03 appears to invoke four steps to restore to 2311 volumes. The write up says to respond to 4307A prompts at three steps by entering “22 <enter>” if using 3270 Telnet or “ext” if using console.

After seeing the 4307A prompt after the first step I entered “ext”, and things ground to a halt.

See attached screen shot. I guess I’m getting ambushed dealing with how to reply to prompts.

What should I do next? Thanks!

Michael

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Monday, November 21, 2016 4:24 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Michael:

OK, then it would appear that you are on step MIGRATE01, the first IPL of the restored distribution system, and that you have restored all tapes.  But based on what you say about Jason and tn3270, you have not seen much to let you know if the restores worked.  

I am not familiar with the Jason GUI...do you have a link?

DOS/360 did not have any support for 3270 devices as an operator console, so tn3270 will not help much either.  

And Hercules 3.07 did not support a wide range of telnet clients.  In particular, PuTTY will not connect.  I used a Windows NT Telnet client, which will not work so well on a Linux system if that's what you are using.  

I suggest you repeat the process using the Hercules integrated console.  The statements to do this are commented in the CNF files.  Just uncomment them, comment the original console statements, and prefix reponses to the restore program with a \ (backwards slash).  

That should give you console output to let you (and us) see how the restores are doing.  And if they fail, we can see logs that will help diagnose this.  

I agree with Mike that DOS/VS release 34 is more polished--it was in real life too--but I had a great time messing around with DOS/360--again, in real life too.  In the age of iPhones and GUI's, it's interesting to see what things were like 50 years ago.  

Best Regards,
Steve Orso


---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi, Steve.  Thanks for following up - much appreciated!

Yes, I'm following your instructions. And, yes, I was trying to IPL from the 2311 on 132.

I think the first thing to fall back to is to delete everything and start over from the beginning.  I'll report back on how it goes.

Couple questions.  First, I was using the Jason GUI - could that have anything to do  with things?  Second, I have attempted to see the console output both using  Jason as well as using tn3270.  No dice.  How would you recommend connecting to see console output?

Again, many  thanks.

Michael




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Michael,


There are two consoles when you run an OS on Hercules.
One is for Hercules, so you can control the emulated hardware.
The other is either a Telnet or TN3270 emulator so you can send commands to the emulated OS.
Since DOS/360 doesn't support 3270 (or TN3270) as a console, a telnet client has to be used.


The "22<enter>" is typed into the DOS/360 Telnet console, and the "ext" is typed into the Hercules console.


The Hercules "EXT" command simulates an external interrupt which "wakes up" DOS/360 and tells it there is work to be done


I use TeraTerm as my telnet client when doing things like this. From experience, I have my TeraTerm terminal settings "New-Line" set to transmit CR+LF always, receive new-line is set to auto, and local echo is turned on.


There should be similar settings for whichever telnet program you are using.


I have probably sown enough confusion for now.


Mark Gutzwiller

[[e-mail] [hercules-390]]

Thanks, Mark. Sounds like I’ll need to get that telnet client before going further. Since only the first script was attempted, I suppose I can just step back and delete that first 2311 – then recreate the volume with the dasdinit, start hercules, and retry the script, this time responding by both consoles. Hopefully, I don’t have to start all over again – does that sound right?

Can you tell me how to attach images to these conversations here in YahooGroups?

Michael

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Saturday, December 10, 2016 12:46 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Michael,

There are two consoles when you run an OS on Hercules.
One is for Hercules, so you can control the emulated hardware.
The other is either a Telnet or TN3270 emulator so you can send commands to the emulated OS.
Since DOS/360 doesn't support 3270 (or TN3270) as a console, a telnet client has to be used. 

The "22<enter>" is typed into the DOS/360 Telnet console, and the "ext" is typed into the Hercules console. 

The Hercules "EXT" command simulates an external interrupt which "wakes up" DOS/360 and tells it there is work to be done

I use TeraTerm as my telnet client when doing things like this. From experience, I have my TeraTerm terminal settings "New-Line" set to transmit CR+LF always, receive new-line is set to auto, and local echo is turned on.

There should be similar settings for whichever telnet program you are using.

I have probably sown enough confusion for now.

Mark Gutzwiller




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

- - - In hercules-***@yahoogroups.com, <***@...> wrote:
> Thanks, Mark. Sounds like I’ll need to get that telnet client before going further.
>Since only the first script was attempted, I suppose I can just step back and
>delete that first 2311 – then recreate the volume with the dasdinit, start hercules,
>and retry the script, this time responding by both consoles. Hopefully, I don’t
>have to start all over again – does that sound right?
> Can you tell me how to attach images to these conversations here in YahooGroups?
> Michael
- - - old notes snipped - - -

The owners of most Hercules yahoo groups do not allow attachments.
You could up load to the files section but for your issue, using
copy/paste of the text from the consoles would have been better.

Using line-mode telnet consoles can get complicated.
It is much easier to use a Hercules integrated console.
Just add a -c to the device definition in the Hercules
configuration file.
0009 1052 becomes 0009 1052-c
01F 3215 becomes 01F 3215-c

That way the DOS line-mode console and Hercules console
are the same console. Prefix any DOS commands with the
command character for that console.
For example, you could have replied:
either:
/22
or:
ext
with the 22 going to DOS or the ext going to Hercules.

No telnet client needed.
No weird IPL timings of starting Hercules,
starting some telnet client,
and then IPLing.
Much closer to a non-emulated system.

[[e-mail] [hercules-390]]

To me, that sounds right.

As somitcw stated in another response, Hercules also has an integrated console which may be easier.
In the dos360.cnf config file, there are these lines:


# Console Printer/Keyboard
001F 1052 noprompt
##001F 1052-c \ noprompt #optional; uses Hercules console instead of telnet.


You would just need to add a "#" at the beginning of the line for the 1052, and remove the "##" for the 1052-c.
The "\" is the prefix character, used to send commands to DOS360 instead of to Hercules. You can leave it as is, or change it to "/".


As for attachments, it's just as somitcw says in his response.

Good luck.


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Thanks, Mark. Sounds like I’ll need to get that telnet client before going further. Since only the first script was attempted, I suppose I can just step back and delete that first 2311 – then recreate the volume with the dasdinit, start hercules, and retry the script, this time responding by both consoles. Hopefully, I don’t have to start all over again – does that sound right?

Can you tell me how to attach images to these conversations here in YahooGroups?

Michael

Sent from my Windows 10 phone

From: ***@... mailto:***@... [hercules-390]
Sent: Saturday, December 10, 2016 12:46 AM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Michael,

There are two consoles when you run an OS on Hercules.
One is for Hercules, so you can control the emulated hardware.
The other is either a Telnet or TN3270 emulator so you can send commands to the emulated OS.
Since DOS/360 doesn't support 3270 (or TN3270) as a console, a telnet client has to be used.

The "22<enter>" is typed into the DOS/360 Telnet console, and the "ext" is typed into the Hercules console.

The Hercules "EXT" command simulates an external interrupt which "wakes up" DOS/360 and tells it there is work to be done

I use TeraTerm as my telnet client when doing things like this. From experience, I have my TeraTerm terminal settings "New-Line" set to transmit CR+LF always, receive new-line is set to auto, and local echo is turned on.

There should be similar settings for whichever telnet program you are using.

I have probably sown enough confusion for now.

Mark Gutzwiller




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Ahh! NOW I get it – I didn’t grasp the role of the “/” when responding to the telnet console prompt. May thanks!

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Saturday, December 10, 2016 4:35 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
To me, that sounds right. 

As somitcw stated in another response, Hercules also has an integrated console which may be easier.
In the dos360.cnf config file, there are these lines:

# Console Printer/Keyboard
001F 1052 noprompt 
##001F 1052-c \ noprompt #optional; uses Hercules console instead of telnet.

You would just need to add a "#" at the beginning of the line for the 1052, and remove the "##" for the 1052-c.
The "\" is the prefix character, used to send commands to DOS360 instead of to Hercules. You can leave it as is, or change it to "/".

As for attachments, it's just as somitcw says in his response.

Good luck.

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Thanks, Mark. Sounds like I’ll need to get that telnet client before going further. Since only the first script was attempted, I suppose I can just step back and delete that first 2311 – then recreate the volume with the dasdinit, start hercules, and retry the script, this time responding by both consoles. Hopefully, I don’t have to start all over again – does that sound right?

Can you tell me how to attach images to these conversations here in YahooGroups?

Michael

Sent from my Windows 10 phone

From: ***@... [hercules-390]
Sent: Saturday, December 10, 2016 12:46 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Michael,

There are two consoles when you run an OS on Hercules.
One is for Hercules, so you can control the emulated hardware.
The other is either a Telnet or TN3270 emulator so you can send commands to the emulated OS.
Since DOS/360 doesn't support 3270 (or TN3270) as a console, a telnet client has to be used. 

The "22<enter>" is typed into the DOS/360 Telnet console, and the "ext" is typed into the Hercules console. 

The Hercules "EXT" command simulates an external interrupt which "wakes up" DOS/360 and tells it there is work to be done

I use TeraTerm as my telnet client when doing things like this. From experience, I have my TeraTerm terminal settings "New-Line" set to transmit CR+LF always, receive new-line is set to auto, and local echo is turned on.

There should be similar settings for whichever telnet program you are using.

I have probably sown enough confusion for now.

Mark Gutzwiller




[Non-text portions of this message have been removed]

 




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Ok, I’ve rerun through the end of the DISTRIB section. Net would be the MIGRATE stage.

Before go further, let me ask something: I noticed two or three errors along the way, something. about ‘Addressing exception. The scripts proceeded on without other issues.

Is this normal?

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Saturday, December 10, 2016 4:35 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
To me, that sounds right. 

As somitcw stated in another response, Hercules also has an integrated console which may be easier.
In the dos360.cnf config file, there are these lines:

# Console Printer/Keyboard
001F 1052 noprompt 
##001F 1052-c \ noprompt #optional; uses Hercules console instead of telnet.

You would just need to add a "#" at the beginning of the line for the 1052, and remove the "##" for the 1052-c.
The "\" is the prefix character, used to send commands to DOS360 instead of to Hercules. You can leave it as is, or change it to "/".

As for attachments, it's just as somitcw says in his response.

Good luck.

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Thanks, Mark. Sounds like I’ll need to get that telnet client before going further. Since only the first script was attempted, I suppose I can just step back and delete that first 2311 – then recreate the volume with the dasdinit, start hercules, and retry the script, this time responding by both consoles. Hopefully, I don’t have to start all over again – does that sound right?

Can you tell me how to attach images to these conversations here in YahooGroups?

Michael

Sent from my Windows 10 phone

From: ***@... [hercules-390]
Sent: Saturday, December 10, 2016 12:46 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Michael,

There are two consoles when you run an OS on Hercules.
One is for Hercules, so you can control the emulated hardware.
The other is either a Telnet or TN3270 emulator so you can send commands to the emulated OS.
Since DOS/360 doesn't support 3270 (or TN3270) as a console, a telnet client has to be used. 

The "22<enter>" is typed into the DOS/360 Telnet console, and the "ext" is typed into the Hercules console. 

The Hercules "EXT" command simulates an external interrupt which "wakes up" DOS/360 and tells it there is work to be done

I use TeraTerm as my telnet client when doing things like this. From experience, I have my TeraTerm terminal settings "New-Line" set to transmit CR+LF always, receive new-line is set to auto, and local echo is turned on.

There should be similar settings for whichever telnet program you are using.

I have probably sown enough confusion for now.

Mark Gutzwiller




[Non-text portions of this message have been removed]

 




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Yes, that's normal.



Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Ok, I’ve rerun through the end of the DISTRIB section. Net would be the MIGRATE stage.

Before go further, let me ask something: I noticed two or three errors along the way, something. about ‘Addressing exception. The scripts proceeded on without other issues.

Is this normal?

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Hi Folks,

I feel like I’m back to the original obstacle; namely, the inability to IPL when starting the MIGRATE phase. I’m pretty sure I’ve entered the commands exactly as for MIGRATE01.

Below shows the console output – what to do, what to do.
________________________________________________________
Using fthreads instead of pthreads +
Dynamic loading support
Using shared libraries
HTTP Server support
No SIGABEND handler
Regular Expressions support
Automatic Operator support
Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8 fetch_dw store_dw
Running on CHUWI Windows_NT-6.2 i686 MP=4
HHCHD018I Loadable module directory is hercules
Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2010
Active: Message Security Assist
Message Security Assist Extension 1
Message Security Assist Extension 2
HHCCF008E Error in conf/dos360.cnf line 25: Syntax error: LOG
HHCCF065I Hercules: tid=000018FC, pid=9296, pgid=9296, priority=0
HHCDA020I dasd/res11a.2311 cyls=203 heads=10 tracks=2030 trklen=4096
HHCDA020I dasd/res11b.2311 cyls=203 heads=10 tracks=2030 trklen=4096
HHCDA020I dasd/res11c.2311 cyls=203 heads=10 tracks=2030 trklen=4096
HHCDA020I dasd/dosres.2314 cyls=203 heads=20 tracks=4060 trklen=7680
HHCDA020I dasd/spool1.2314 cyls=203 heads=20 tracks=4060 trklen=7680
HHCDA020I dasd/wrk14a.2314 cyls=203 heads=20 tracks=4060 trklen=7680
HHCDA020I dasd/wrk14b.2314 cyls=203 heads=20 tracks=4060 trklen=7680
HHCTE001I Console connection thread started: tid=000020C0, pid=9296
HHCTE003I Waiting for console connection on port 3270
HHCCP002I CPU0000 thread started: tid=00000BF0, pid=9296, priority=15
HHCTT002I Timer thread started: tid=000021A0, pid=9296, priority=0
HHCCP003I CPU0000 architecture mode S/370
HHCPN001I Control panel thread started: tid=000018FC, pid=9296
HHCAO001I Hercules Automatic Operator thread started;
tid=00001398, pri=0, pid=9296
stop
devinit 00e prt/migrate-1-unloadlibs.txt crlf
HHCPN098I Device 0:000E initialized
sh hetinit -d -n tape/migrate-libs.aws
Hercules HET IEHINITT program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
devinit 280 tape/migrate-libs.aws
HHCTA004I 0280: tape/migrate-libs.aws is a AWS Format tape file
HHCPN098I Device 0:0280 initialized
ipl 132
HHCCP029E S/370 mode IPL failed: CSW status=0E00
Sense=000800C8 0000
devinit 00c jcl/migrateipl1.jcl
HHCPN098I Device 0:000C initialized
\(001F)
\(001F) 22
ext
HHCPN050I Interrupt key depressed
Command ==>





From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Sunday, December 11, 2016 12:04 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Yes, that's normal.


Mark Gutzwiller


---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
Ok, I’ve rerun through the end of the DISTRIB section. Net would be the MIGRATE stage.

Before go further, let me ask something: I noticed two or three errors along the way, something. about ‘Addressing exception. The scripts proceeded on without other issues.

Is this normal?

[[e-mail] [hercules-390]]

Could you post your dos360.cnf file?

It will help with trouble shooting.


Thanks.


Mark Gutzwiller

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Here ya go:

#
# Configuration file for Hercules ESA/390 emulator
#
# DOS/360
#
#==================================== Emulator settings

TZOFFSET -0000 # Windows clock set to gmt
TODDRAG 1
ARCHMODE S/370
CNSLPORT 3270 # telnet to localhost:3270
SYSEPOCH 1900 # base date for TOD clock
YROFFSET -28 # move back 28 years to 1988, day-date matches.

#==================================== Emulated cpu settings
CPUSERIAL 000611
CPUMODEL 2040 # s/360-40
OSTAILOR VSE
MAINSIZE 2 # 2MB main storage, unheard of for DOS.
# and minimum for hercules
XPNDSIZE 0
NUMCPU 1
LOADPARM ........

LOG herclog.log

DEFSYM line-end-type "crlf" # line endings; "crlf" for Windows, "" for *nix & Mac.


#==================================== Defined Devices

#------------------------------------ Unit record equipment
000C 2501 jcl/operipl.jcl trunc ascii eof
000D 3525 pch00d.txt ascii ${line-end-type}
000E 1403 prt00e.txt crlf

001C 2501 * trunc ascii eof
001D 3525 pch01d.txt ascii ${line-end-type}
001E 1403 prt01e.txt crlf

002C 2501 * trunc ascii eof
002D 3525 pch02d.txt ascii ${line-end-type}
002E 1403 prt02e.txt crlf

# Console Printer/Keyboard
##001F 1052 noprompt
001F 1052-c \ noprompt #optional; uses Hercules console instead of telnet.


#------------------------------------ Distribution Disk Packs
#
0130 2311 dasd/res11a.2311 # sysres, core image, relo
0131 2311 dasd/res11b.2311 # sysres, core image, system source
0132 2311 dasd/res11c.2311 # sysres, system relo, private libs


#------------------------------------ Target System Disk Packs

190 2314 dasd/dosres.2314 # target system residence file
191 2314 dasd/spool1.2314 # POWER II spooling disk
192 2314 dasd/wrk14a.2314 # work files for bg
193 2314 dasd/wrk14b.2314 # work files for f2

#------------------------------------ Tape drives

0280 3420
0281 3420
0282 3420
0283 3420
0284 3420
0285 3420
0286 3420
0287 3420

#------------------------------------ Display devices

00A0.6 3270
00A6.2 3270 PRINTER # DEFINED AS 3287 IN DOS/360 SUPERVISOR



From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, December 12, 2016 6:11 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Could you post your dos360.cnf file?

It will help with trouble shooting.

Thanks.

Mark Gutzwiller

[[e-mail] [hercules-390]]

Okay, I've started this install from scratch, and I am running into problems at the distrib04 stage.

I am working through it, and will report back what I find.


Mark Gutzwiller

[[e-mail] [hercules-390]]

Okay, after trying it several times, it looks like, for some reason, steps distrib04 and distrib06 need to be done twice. I receive errors the first time each one is run, but the second time for each they run okay. EOJ is printed for both..

After finishing all the distrib stages, I can IPL 132 okay (migrate01 stage).


Mark Gutzwiller

---In hercules-***@yahoogroups.com, <***@...> wrote :

Hi Folks,

I feel like I’m back to the original obstacle; namely, the inability to IPL when starting the MIGRATE phase. I’m pretty sure I’ve entered the commands exactly as for MIGRATE01.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

If I recall correctly, those are the two scripts that coughed up hairballs about addressing exceptions.

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, December 12, 2016 7:12 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Okay, after trying it several times, it looks like, for some reason, steps distrib04 and distrib06 need to be done twice. I receive errors the first time each one is run, but the second time for each they run okay. EOJ is printed for both..

After finishing all the distrib stages, I can IPL 132 okay (migrate01 stage).


Mark Gutzwiller

---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
Hi Folks,

I feel like I’m back to the original obstacle; namely, the inability to IPL when starting the MIGRATE phase. I’m pretty sure I’ve entered the commands exactly as for MIGRATE01.

[[e-mail] [hercules-390]]

In both steps, the tapes are mounted right before IPL. I wonder if Hercules is still mounting the tapes when it tries to IPL?
I wonder if a "stopall" should be added after the devinit as a delay?



---In hercules-***@yahoogroups.com, <***@...> wrote :

If I recall correctly, those are the two scripts that coughed up hairballs about addressing exceptions.

[[e-mail] [hercules-390]]

I use the "pause" command extensively
to avoid timing issues, such as:

pause 1

or

pause 10 (for 10 seconds).

I think your theory is certainly plausible.

BFN. Paul.




---In hercules-***@yahoogroups.com, <***@...> wrote :

In both steps, the tapes are mounted right before IPL. I wonder if Hercules is still mounting the tapes when it tries to IPL?
I wonder if a "stopall" should be added after the devinit as a delay?



---In hercules-***@yahoogroups.com, <***@...> wrote :

If I recall correctly, those are the two scripts that coughed up hairballs about addressing exceptions.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Well, I guess I could try and run the two scripts, with a pause added, and – if it goes south – the worst case is start over again.

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, December 12, 2016 7:42 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


In both steps, the tapes are mounted right before IPL.
I wonder if Hercules is still mounting the tapes when it tries to IPL?
I wonder if a "stopall" should be added after the devinit as a delay?


---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
If I recall correctly, those are the two scripts that coughed up hairballs about addressing exceptions.

[[e-mail] [hercules-390]]

I tried using the pause in both scripts, and It didn't work. I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and distrib06.rc, and they ran without problems. I did the whole thing from scratch 4 times, and this could be the solution, or a cheap work-around.




Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Well, I guess I could try and run the two scripts, with a pause added, and – if it goes south – the worst case is start over again.

[[e-mail] [hercules-390]]

Hi Mark:

Yeah, that was one of the things I planned to test. Many thanks for giving it a shot.


sysclear would clear the pending I/O operation to the console that I presume is confusing the very primitive disk initialization utilities.


I will update the scripts to include sysclears prior to the IPL of the tapes.



You are right, more people are interested in MVS or VM; I really haven't gotten much feedback on DOS/360. And DOS/360 is really more of a history lesson than an operating system capable of doing "real" work...DOS/VS, MVS 3.8j, or one of the several good turnkey systems are better choices for doing real work.


I created it about a year ago when I first learned of Hercules' existence, and I have a DOS/VS install put together from a couple of the guides that have been published here.


But--as happens to me--I got sidetracked on another interesting project. :-)


My thanks to you and Michael for working with this.


Best Regards,
Steve Orso.





---In hercules-***@yahoogroups.com, <***@...> wrote :

I tried using the pause in both scripts, and It didn't work. I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and distrib06.rc, and they ran without problems. I did the whole thing from scratch 4 times, and this could be the solution, or a cheap work-around.




Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Well, I guess I could try and run the two scripts, with a pause added, and – if it goes south – the worst case is start over again.

[[e-mail] [hercules-390]]

Stephen et al, Funny you say “history lesson” because nostalgia is what all this is about for me. I remember the first time I set eyes on that big red System/360-40. For me – a cub programmer who had only seen unit record, 1401 and 7070 systems – it was like touching the USS Starship Enterprise. It was a wonderful day when I lugged over and read in the tray of cards comprising my first COBOL program. It means so much to me – now retired and out to pasture – to be able to relive, just a little, what were truly happy days.

I’m fighting bronchitis right now and not feeling too chipper, but will soon get back on this project to try out the revised scripts. I really appreciate the help from all of you!

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Tuesday, December 13, 2016 2:03 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Mark:

Yeah, that was one of the things I planned to test.  Many thanks for giving it a shot.  

sysclear would clear the pending I/O operation to the console that I presume is confusing the very primitive disk initialization utilities.  

I will update the scripts to include sysclears prior to the IPL of the tapes.  


You are right, more people are interested in MVS or VM; I really haven't gotten much feedback on DOS/360.  And DOS/360 is really more of a history lesson than an operating system capable of doing "real" work...DOS/VS, MVS 3.8j, or one of the several good turnkey systems are better choices for doing real work.   

I created it about a year ago when I first learned of Hercules' existence, and I have a DOS/VS install put together from a couple of the guides that have been published here.  

But--as happens to me--I got sidetracked on another interesting project.  :-)

My thanks to you and Michael for working with this.  

Best Regards,
Steve Orso. 




---In hercules-***@yahoogroups.com, <***@...> wrote :
I tried using the pause in both scripts, and It didn't work.
I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and distrib06.rc, and they ran without problems. I did the whole thing from scratch 4 times, and this could be the solution, or a cheap work-around.


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Well, I guess I could try and run the two scripts, with a pause added, and – if it goes south – the worst case is start over again.
 





[Non-text portions of this message have been removed]

[Mike Stramba [e-mail] [hercules-390]]

Hmm

Strange ..

When running distrib05.rc, Hercules 3.12 seems to be ignoring the
'stopall' command in the rc file, saying "IPL rejected, all cpu's must
be stopped".

Mike

On 12/13/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Stephen et al, Funny you say “history lesson” because nostalgia is what all
> this is about for me. I remember the first time I set eyes on that big red
> System/360-40. For me – a cub programmer who had only seen unit record,
> 1401 and 7070 systems – it was like touching the USS Starship Enterprise.
> It was a wonderful day when I lugged over and read in the tray of cards
> comprising my first COBOL program. It means so much to me – now retired and
> out to pasture – to be able to relive, just a little, what were truly happy
> days.
>
> I’m fighting bronchitis right now and not feeling too chipper, but will soon
> get back on this project to try out the revised scripts. I really
> appreciate the help from all of you!
>
> Sent from my Windows 10 phone
>
> From: ***@yahoo.com [hercules-390]
> Sent: Tuesday, December 13, 2016 2:03 PM
> To: hercules-***@yahoogroups.com
> Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
>
>
> Hi Mark:
>
> Yeah, that was one of the things I planned to test.  Many thanks for giving
> it a shot.
>
> sysclear would clear the pending I/O operation to the console that I presume
> is confusing the very primitive disk initialization utilities.
>
> I will update the scripts to include sysclears prior to the IPL of the
> tapes.
>
>
> You are right, more people are interested in MVS or VM; I really haven't
> gotten much feedback on DOS/360.  And DOS/360 is really more of a history
> lesson than an operating system capable of doing "real" work...DOS/VS, MVS
> 3.8j, or one of the several good turnkey systems are better choices for
> doing real work.
>
> I created it about a year ago when I first learned of Hercules' existence,
> and I have a DOS/VS install put together from a couple of the guides that
> have been published here.
>
> But--as happens to me--I got sidetracked on another interesting project.
>  :-)
>
> My thanks to you and Michael for working with this.
>
> Best Regards,
> Steve Orso.
>
>
>
>
> ---In hercules-***@yahoogroups.com, <***@...> wrote :
> I tried using the pause in both scripts, and It didn't work.
> I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and
> distrib06.rc, and they ran without problems. I did the whole thing from
> scratch 4 times, and this could be the solution, or a cheap work-around.
>
>
> Mark Gutzwiller
>
>
> ---In hercules-***@yahoogroups.com, <***@...> wrote :
> Well, I guess I could try and run the two scripts, with a pause added, and –
> if it goes south – the worst case is start over again.
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>

[Mike Stramba [e-mail] [hercules-390]]

When I run job power07.jcl, I'm getting :

1C10A PLEASE ASSIGN SYSLNK.

What is the response ?

Or did I miss something in power06 (start power ) ?

Mike

On 12/13/16, Mike Stramba <***@gmail.com> wrote:
> Hmm
>
> Strange ..
>
> When running distrib05.rc, Hercules 3.12 seems to be ignoring the
> 'stopall' command in the rc file, saying "IPL rejected, all cpu's must
> be stopped".
>
> Mike
>
> On 12/13/16, ***@mac.com [hercules-390]
> <hercules-***@yahoogroups.com> wrote:
>> Stephen et al, Funny you say “history lesson” because nostalgia is what
>> all
>> this is about for me. I remember the first time I set eyes on that big
>> red
>> System/360-40. For me – a cub programmer who had only seen unit record,
>> 1401 and 7070 systems – it was like touching the USS Starship Enterprise.
>> It was a wonderful day when I lugged over and read in the tray of cards
>> comprising my first COBOL program. It means so much to me – now retired
>> and
>> out to pasture – to be able to relive, just a little, what were truly
>> happy
>> days.
>>
>> I’m fighting bronchitis right now and not feeling too chipper, but will
>> soon
>> get back on this project to try out the revised scripts. I really
>> appreciate the help from all of you!
>>
>> Sent from my Windows 10 phone
>>
>> From: ***@yahoo.com [hercules-390]
>> Sent: Tuesday, December 13, 2016 2:03 PM
>> To: hercules-***@yahoogroups.com
>> Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
>>
>>
>> Hi Mark:
>>
>> Yeah, that was one of the things I planned to test.  Many thanks for
>> giving
>> it a shot.
>>
>> sysclear would clear the pending I/O operation to the console that I
>> presume
>> is confusing the very primitive disk initialization utilities.
>>
>> I will update the scripts to include sysclears prior to the IPL of the
>> tapes.
>>
>>
>> You are right, more people are interested in MVS or VM; I really haven't
>> gotten much feedback on DOS/360.  And DOS/360 is really more of a history
>> lesson than an operating system capable of doing "real" work...DOS/VS,
>> MVS
>> 3.8j, or one of the several good turnkey systems are better choices for
>> doing real work.
>>
>> I created it about a year ago when I first learned of Hercules'
>> existence,
>> and I have a DOS/VS install put together from a couple of the guides that
>> have been published here.
>>
>> But--as happens to me--I got sidetracked on another interesting project.
>>  :-)
>>
>> My thanks to you and Michael for working with this.
>>
>> Best Regards,
>> Steve Orso.
>>
>>
>>
>>
>> ---In hercules-***@yahoogroups.com, <***@...> wrote :
>> I tried using the pause in both scripts, and It didn't work.
>> I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and
>> distrib06.rc, and they ran without problems. I did the whole thing from
>> scratch 4 times, and this could be the solution, or a cheap work-around.
>>
>>
>> Mark Gutzwiller
>>
>>
>> ---In hercules-***@yahoogroups.com, <***@...> wrote :
>> Well, I guess I could try and run the two scripts, with a pause added, and
>> –
>> if it goes south – the worst case is start over again.
>>
>>
>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>

[Martin Truebner [e-mail] [hercules-390]]

Mike,

>> 1C10A PLEASE ASSIGN SYSLNK.

that sounds pretty much like some JCL went where it should not go.

the message is result of a // OPTION CATAL in a partition where SYSLNK
is not assigned. In antediluvian times a link job (where the // OPTION
CATAL does belong) did normaly run only in BG. Lots of work to do it
in other partitions as well.

- so in conclusion:

>> Or did I miss something in power06 (start power ) ?

yes that is what it sounds like to be.

Martin

[Mike Stramba [e-mail] [hercules-390]]

Hi Martin,

All good now ;) I re-ran the power start up sequence.

Mike

On 12/14/16, Martin Truebner ***@pi-sysprog.de [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Mike,
>
>>> 1C10A PLEASE ASSIGN SYSLNK.
>
> that sounds pretty much like some JCL went where it should not go.
>
> the message is result of a // OPTION CATAL in a partition where SYSLNK
> is not assigned. In antediluvian times a link job (where the // OPTION
> CATAL does belong) did normaly run only in BG. Lots of work to do it
> in other partitions as well.
>
> - so in conclusion:
>
>>> Or did I miss something in power06 (start power ) ?
>
> yes that is what it sounds like to be.
>
> Martin
>

[[e-mail] [hercules-390]]

Hi Steve,

I had the same problem with MIGRATE03. I hit enter on the telnet console, but perhaps add "sysclear" to the "On Hercules section?


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Hi Mark:

Yeah, that was one of the things I planned to test. Many thanks for giving it a shot.


sysclear would clear the pending I/O operation to the console that I presume is confusing the very primitive disk initialization utilities.

[[e-mail] [hercules-390]]

Oh my 
 now I can’t get past distrib02 & 03. Even with liberally using STOPALL and SYSCLEAR. IPLs fail.

My bronchitis is winning tonight, so have to stop for tonight. Guess I’ll need to erase and reinstall it all and start again tomorrow.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Tuesday, December 13, 2016 5:31 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Steve,

I had the same problem with MIGRATE03. I hit enter on the telnet console, but perhaps add "sysclear" to the "On Hercules section?

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi Mark:

Yeah, that was one of the things I planned to test.  Many thanks for giving it a shot.  

sysclear would clear the pending I/O operation to the console that I presume is confusing the very primitive disk initialization utilities.  






[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Steve, When you update the scripts, would you please also add in the write up each place where a “\22” or “ext” response should be entered? While one section shows the 22s in bold, in another paragraph you allude to needing to enter some more of these responses but it’s not clear whether one or both or whatever.

Thanks! After your edits, I’m gonna nuke and pave from the beginning again.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Tuesday, December 13, 2016 2:03 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Mark:

Yeah, that was one of the things I planned to test.  Many thanks for giving it a shot.  

sysclear would clear the pending I/O operation to the console that I presume is confusing the very primitive disk initialization utilities.  

I will update the scripts to include sysclears prior to the IPL of the tapes.  


You are right, more people are interested in MVS or VM; I really haven't gotten much feedback on DOS/360.  And DOS/360 is really more of a history lesson than an operating system capable of doing "real" work...DOS/VS, MVS 3.8j, or one of the several good turnkey systems are better choices for doing real work.   

I created it about a year ago when I first learned of Hercules' existence, and I have a DOS/VS install put together from a couple of the guides that have been published here.  

But--as happens to me--I got sidetracked on another interesting project.  :-)

My thanks to you and Michael for working with this.  

Best Regards,
Steve Orso. 




---In hercules-***@yahoogroups.com, <***@...> wrote :
I tried using the pause in both scripts, and It didn't work.
I finally put "SYSCLEAR" after the "STOPALL" in both distrib04.rc and distrib06.rc, and they ran without problems. I did the whole thing from scratch 4 times, and this could be the solution, or a cheap work-around.


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Well, I guess I could try and run the two scripts, with a pause added, and – if it goes south – the worst case is start over again.
 





[Non-text portions of this message have been removed]

[Mike Stramba [e-mail] [hercules-390]]

On 12/14/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Thanks! After your edits, I’m gonna nuke and pave from the beginning
> again.

It shouldn't be necessary to "nuke".

Going back to "distrib01" will be sufficient, as that re-initializes your dasd.

The issue seems to be (I ran into it too), with the "22 ext" sequence
in the restore steps.

I *think* I may have entered "one too many '22 exts', at one point
where "EOJ" had already been posted. That in turn messes up the next
step which is depending on the tape being "positioned" from the
previous step.

I also used an external telnet client (copied from my XP box to my Win7 box).

I'll try using the Hercules integrated telnet, to see what issues if
any that causes.

Mike

[[e-mail] [hercules-390]]

Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at the tail end of DISTRIB03. The web writeup lists the following console output:

3008
0280
2E0F
4022A

My hercules console output shows:

3008
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
.
. [three more lines of hex numbers about 0280]
.
HHCCP077I 0280:Sense=INTREQ EOC WRI
0280
260F
4002A

Notice how the last two prompts differ between the write up versus execution.

Does this mean anything? Especially as it relates to what responses should be entered next.

Sent from my Windows 10 phone

From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Wednesday, December 14, 2016 5:40 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
On 12/14/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Thanks! After your edits, I’m gonna nuke and pave from the beginning
> again.

It shouldn't be necessary to "nuke".

Going back to "distrib01" will be sufficient, as that re-initializes your dasd.

The issue seems to be (I ran into it too), with the "22 ext" sequence
in the restore steps.

I *think* I may have entered "one too many '22 exts', at one point
where "EOJ" had already been posted. That in turn messes up the next
step which is depending on the tape being "positioned" from the
previous step.

I also used an external telnet client (copied from my XP box to my Win7 box).

I'll try using the Hercules integrated telnet, to see what issues if
any that causes.

Mike




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Actually, I’m thinking that what I respond next here may be important. Steve’s web write up doesn’t specify what should be the correct next response, irrespective of whether Hercules is prompting with 4022A or 4002A.

I’ve saved off copies of my files that are currently in the \dasd folder, so I can pick up from here. I’m going to wait on further discussion here about how to proceed.

Thanks!

Sent from my Windows 10 phone

From: ***@mac.com [hercules-390]
Sent: Wednesday, December 14, 2016 6:45 PM
To: Mike Stramba ***@gmail.com [hercules-390]
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at the tail end of DISTRIB03. The web writeup lists the following console output:

3008
0280
2E0F
4022A

My hercules console output shows:

3008
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
.
. [three more lines of hex numbers about 0280]
.
HHCCP077I 0280:Sense=INTREQ EOC WRI
0280
260F
4002A

Notice how the last two prompts differ between the write up versus execution.

Does this mean anything? Especially as it relates to what responses should be entered next.

Sent from my Windows 10 phone

From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Wednesday, December 14, 2016 5:40 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
On 12/14/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
>
> Thanks! After your edits, I’m gonna nuke and pave from the beginning
> again.

It shouldn't be necessary to "nuke".

Going back to "distrib01" will be sufficient, as that re-initializes your dasd.

The issue seems to be (I ran into it too), with the "22 ext" sequence
in the restore steps.

I *think* I may have entered "one too many '22 exts', at one point
where "EOJ" had already been posted. That in turn messes up the next
step which is depending on the tape being "positioned" from the
previous step.

I also used an external telnet client (copied from my XP box to my Win7 box).

I'll try using the Hercules integrated telnet, to see what issues if
any that causes.

Mike

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

This is what I have at the end of that distrib03:
16:24:04 024425 RECORDS RESTORED FOR ABOVE FILE
16:24:04 3007
16:24:04 END OF JOB
16:24:04 3008
16:24:04 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
16:24:04 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6 00090000 0000024425.F....
16:24:04 HHCCP075I 0280:Stat=2E00 Count=0001
16:24:04 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF FF000000
16:24:04 HHCCP077I 0280:Sense=INTREQ EOC WRI
16:24:04 0280
16:24:04 2E0F
16:24:04 4022A



I looked for the "RECORDS RESTORED..." and "END OF JOB". it's easy to miss with all the Hercules messages. EDIT > FIND helped a lot.


If you see that, it's okay to continue with DISTRIB04.


Mark Gutzwiller







---In hercules-***@yahoogroups.com, <***@...> wrote :

Actually, I’m thinking that what I respond next here may be important. Steve’s web write up doesn’t specify what should be the correct next response, irrespective of whether Hercules is prompting with 4022A or 4002A.

I’ve saved off copies of my files that are currently in the \dasd folder, so I can pick up from here. I’m going to wait on further discussion here about how to proceed.

Thanks!

Sent from my Windows 10 phone

From: ***@... mailto:***@... [hercules-390]
Sent: Wednesday, December 14, 2016 6:45 PM
To: Mike Stramba ***@... mailto:***@... [hercules-390]
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at the tail end of DISTRIB03. The web writeup lists the following console output:

3008
0280
2E0F
4022A

My hercules console output shows:

3008
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
.
. [three more lines of hex numbers about 0280]
.
HHCCP077I 0280:Sense=INTREQ EOC WRI
0280
260F
4002A

Notice how the last two prompts differ between the write up versus execution.

Does this mean anything? Especially as it relates to what responses should be entered next.

Sent from my Windows 10 phone

[[e-mail] [hercules-390]]

Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 7:26 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
This is what I have at the end of that distrib03:

16:24:04 024425 RECORDS RESTORED FOR ABOVE FILE
16:24:04 3007 
16:24:04 END OF JOB
16:24:04 3008 
16:24:04 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
16:24:04 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6 00090000 0000024425.F....
16:24:04 HHCCP075I 0280:Stat=2E00 Count=0001 
16:24:04 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF FF000000
16:24:04 HHCCP077I 0280:Sense=INTREQ EOC WRI 
16:24:04 0280 
16:24:04 2E0F 
16:24:04 4022A

I looked for the "RECORDS RESTORED..." and "END OF JOB". it's easy to miss with all the Hercules messages. EDIT > FIND helped a lot.


If you see that, it's okay to continue with DISTRIB04.


Mark Gutzwiller





---In hercules-***@yahoogroups.com, <***@...> wrote :
Actually, I’m thinking that what I respond next here may be important. Steve’s web write up doesn’t specify what should be the correct next response, irrespective of whether Hercules is prompting with 4022A or 4002A.

I’ve saved off copies of my files that are currently in the \dasd folder, so I can pick up from here. I’m going to wait on further discussion here about how to proceed.

Thanks!

Sent from my Windows 10 phone

From: ***@... [hercules-390]
Sent: Wednesday, December 14, 2016 6:45 PM
To: Mike Stramba ***@... [hercules-390]
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at the tail end of DISTRIB03. The web writeup lists the following console output:

3008
0280
2E0F
4022A

My hercules console output shows:

3008
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
.
. [three more lines of hex numbers about 0280]
.
HHCCP077I 0280:Sense=INTREQ EOC WRI
0280
260F
4002A

Notice how the last two prompts differ between the write up versus execution.

Does this mean anything? Especially as it relates to what responses should be entered next.

Sent from my Windows 10 phone





[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Ok, may be mute point right now – the command window closed itself. <sigh>

Sent from my Windows 10 phone

From: ***@mac.com [hercules-390]
Sent: Wednesday, December 14, 2016 7:30 PM
To: ***@yahoo.com [hercules-390]
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 7:26 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
This is what I have at the end of that distrib03:

16:24:04 024425 RECORDS RESTORED FOR ABOVE FILE
16:24:04 3007 
16:24:04 END OF JOB
16:24:04 3008 
16:24:04 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
16:24:04 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6 00090000 0000024425.F....
16:24:04 HHCCP075I 0280:Stat=2E00 Count=0001 
16:24:04 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF FF000000
16:24:04 HHCCP077I 0280:Sense=INTREQ EOC WRI 
16:24:04 0280 
16:24:04 2E0F 
16:24:04 4022A

I looked for the "RECORDS RESTORED..." and "END OF JOB". it's easy to miss with all the Hercules messages. EDIT > FIND helped a lot.

If you see that, it's okay to continue with DISTRIB04.

Mark Gutzwiller

---In hercules-***@yahoogroups.com, <***@...> wrote :
Actually, I’m thinking that what I respond next here may be important. Steve’s web write up doesn’t specify what should be the correct next response, irrespective of whether Hercules is prompting with 4022A or 4002A.

I’ve saved off copies of my files that are currently in the \dasd folder, so I can pick up from here. I’m going to wait on further discussion here about how to proceed.

Thanks!

Sent from my Windows 10 phone

From: ***@... [hercules-390]
Sent: Wednesday, December 14, 2016 6:45 PM
To: Mike Stramba ***@... [hercules-390]
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at the tail end of DISTRIB03. The web writeup lists the following console output:

3008
0280
2E0F
4022A

My hercules console output shows:

3008
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
.
. [three more lines of hex numbers about 0280]
.
HHCCP077I 0280:Sense=INTREQ EOC WRI
0280
260F
4002A

Notice how the last two prompts differ between the write up versus execution.

Does this mean anything? Especially as it relates to what responses should be entered next.

Sent from my Windows 10 phone

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.

Mark Gutzwiller




---In hercules-***@yahoogroups.com, <***@...> wrote :

Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone

[[e-mail] [hercules-390]]

Ok, will do. Thanks.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 7:45 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.

Mark Gutzwiller



---In hercules-***@yahoogroups.com, <***@...> wrote :
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone




[Non-text portions of this message have been removed]

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Ok, just ran script distrib06. This ended with “CMDREJ”:

script rc/distrib06.rc
# DISTRIB06 Initialize 2314 DOSRES on 190
stopall
devinit 280 tape/k360n-ma108a.aws ro
HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
HHCTA066I 0280: option 'ro' accepted.
HHCPN098I Device 0:0280 initialized
iplc 280
devinit 00c jcl/distrib06.jcl
HHCPN098I Device 0:000C initialized
HHCPN013I EOF reached on SCRIPT file. Processing complete.
HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0) move_character
R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
Command ==>

What should I do next?




From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 7:46 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.

Mark Gutzwiller



---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone

[[e-mail] [hercules-390]]

It's safe to run Distrib06 again. It initalizes a different dasd.

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

Ok, just ran script distrib06. This ended with “CMDREJ”:

script rc/distrib06.rc
# DISTRIB06 Initialize 2314 DOSRES on 190
stopall
devinit 280 tape/k360n-ma108a.aws ro
HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
HHCTA066I 0280: option 'ro' accepted.
HHCPN098I Device 0:0280 initialized
iplc 280
devinit 00c jcl/distrib06.jcl
HHCPN098I Device 0:000C initialized
HHCPN013I EOF reached on SCRIPT file. Processing complete.
HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0) move_character
R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
Command ==>

What should I do next?




From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 7:46 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07




Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.


Mark Gutzwiller





---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@...> wrote :
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone

[[e-mail] [hercules-390]]

OMG – I appear to have successfully completed distrib09.

Will back everything up.

Do I need to do the compression of the 2311 disks, or is that optional?

Thank you for holding my hand thru this tonight! Much appreciated.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 8:25 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
It's safe to run Distrib06 again. It initalizes a different dasd.

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Ok, just ran script distrib06.  This ended with “CMDREJ”:
 
script rc/distrib06.rc
# DISTRIB06 Initialize 2314 DOSRES on 190
stopall
devinit 280 tape/k360n-ma108a.aws ro
HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
HHCTA066I 0280: option 'ro' accepted.
HHCPN098I Device 0:0280 initialized
iplc 280
devinit 00c jcl/distrib06.jcl
HHCPN098I Device 0:000C initialized
HHCPN013I EOF reached on SCRIPT file. Processing complete.
HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
PSW=00000005 C0000020 INST=D2FF11570156 MVC   343(256,1),342(0)      move_character
R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
GR00=00000000  GR01=001FFE00  GR02=00000000  GR03=00000000
GR04=00000000  GR05=00000000  GR06=00000000  GR07=00000000
GR08=00000000  GR09=00000000  GR10=00000000  GR11=00000000
GR12=00000000  GR13=00000000  GR14=00000000  GR15=00000000
HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
Command ==>
 
What should I do next?
 
 
 
 
From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 7:46 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
 
 
Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.
 
Mark Gutzwiller
 


---In hercules-***@yahoogroups.com, <***@...> wrote :
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Great news!

I don't think you really need to, but since you're making a backup, I guess we'll find out.


At step MIGRATE03, after the "stop" on Hercules, you should either enter "sysclear" or the "\" character. I had problems at this point.


Good luck.




Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

OMG – I appear to have successfully completed distrib09.

Will back everything up.

Do I need to do the compression of the 2311 disks, or is that optional?

Thank you for holding my hand thru this tonight! Much appreciated.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

I’ll move on to the MIGRATE stage tomorrow. Had enough excitement for tonight!

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 9:07 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Great news!

I don't think you really need to, but since you're making a backup, I guess we'll find out.

At step MIGRATE03, after the "stop" on Hercules, you should either enter "sysclear" or the "\" character. I had problems at this point.

Good luck.


Mark Gutzwiller


---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
OMG – I appear to have successfully completed distrib09.

Will back everything up.

Do I need to do the compression of the 2311 disks, or is that optional?

Thank you for holding my hand thru this tonight! Much appreciated.

[[e-mail] [hercules-390]]

Okay.

[[e-mail] [hercules-390]]

BTW Mark.

We have no way of knowing who you are
replying to.

If you are using the Yahoo web interface,
if you click on "> show message history"
after you click "reply", then we will know.

BFN. Paul.



---In hercules-***@yahoogroups.com, <***@...> wrote :

Okay.

[[e-mail] [hercules-390]]

Paul,

I am, for Hercules related things. Thanks for the explanation. Just another reason to dislike Yahoo, I guess.


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

BTW Mark.

We have no way of knowing who you are
replying to.

If you are using the Yahoo web interface,
if you click on "> show message history"
after you click "reply", then we will know.

BFN. Paul.

[Kevin Monceaux [e-mail] [hercules-390]]

On Wed, Dec 14, 2016 at 09:40:08PM -0800, ***@yahoo.com.au [hercules-390] wrote:

> We have no way of knowing who you are replying to.

Some of "we" do know who he's replying to. I follow the list via e-mail and
my threaded mail client show exactly who he replied to.




--

Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.

[[e-mail] [hercules-390]]

---In hercules-***@yahoogroups.com, <***@...> wrote :

>> We have no way of knowing who you are replying to.

> Some of "we" do know who he's replying to.
> I follow the list via e-mail and my threaded
> mail client show exactly who he replied to.

Thanks. I didn't know that. I'll be more
specific next time. :-)

BFN. Paul.

[[e-mail] [hercules-390]]

Hi Folks:

Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.


I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.


Redoing 04 or 06 after getting the CMDREJ on 01F is fine...


The compression is optional.....


I will take a look at migrate03.


I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.


Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.


Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.


All comments are welcome...and greatly appreciated.


I second Mark's "Good Luck," and offer "Have Fun!"


Best Regards,
Steve Orso




---In hercules-***@yahoogroups.com, <***@...> wrote :

I’ll move on to the MIGRATE stage tomorrow. Had enough excitement for tonight!

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 9:07 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07




Great news!


I don't think you really need to, but since you're making a backup, I guess we'll find out.



At step MIGRATE03, after the "stop" on Hercules, you should either enter "sysclear" or the "\" character. I had problems at this point.



Good luck.





Mark Gutzwiller



---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@...> wrote :
OMG – I appear to have successfully completed distrib09.

Will back everything up.

Do I need to do the compression of the 2311 disks, or is that optional?

Thank you for holding my hand thru this tonight! Much appreciated.

[[e-mail] [hercules-390]]

Thanks, Steve – I’m thinking i didn’t handle the console responses properly, and that was the root of many of my issues. This last pass I took it slow and also made a point of looking at what was inside each script and deck. That also helped make more sense of the integrated console output.

And, of course, Mark’s steady hand got me through.


Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 9:41 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Folks:

Many thanks for continuing this conversation while I was out of the loop.  And yes, great news, Michael.  Congratulations on getting to distrib09.  

I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.  

Redoing 04 or 06 after getting the CMDREJ on 01F is fine...

The compression is optional.....

I will take a look at migrate03.  

I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet.  It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.  

Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.  

Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them.  I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.  

All comments are welcome...and greatly appreciated. 

I second Mark's "Good Luck," and offer "Have Fun!"

Best Regards,
Steve Orso



---In hercules-***@yahoogroups.com, <***@...> wrote :
I’ll move on to the MIGRATE stage tomorrow.  Had enough excitement for tonight!
 
From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 9:07 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
 
 
Great news!
 
I don't think you really need to, but since you're making a backup, I guess we'll find out.
 
At step MIGRATE03, after the "stop" on Hercules, you should either enter "sysclear" or the "\" character. I had problems at this point.
 
Good luck.
 
 
Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
OMG – I appear to have successfully completed distrib09.

Will back everything up.

Do I need to do the compression of the 2311 disks, or is that optional?

Thank you for holding my hand thru this tonight! Much appreciated.




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

---In hercules-***@yahoogroups.com, <***@...> wrote :

> Thanks, Steve – I’m thinking i didn’t handle
> the console responses properly, and that
> was the root of many of my issues. This
> last pass I took it slow and also made a
> point of looking at what was inside each
> script and deck. That also helped make
> more sense of the integrated console output.

You might want to consider updating the
scripts with "pause" commands to totally
automate the process so that your
success is reproducible.

I would also suggest that you use the
default/normal "/" rather than "\" in the
scripts while using the integrated console.

BFN. Paul.

[[e-mail] [hercules-390]]

Stephen,

I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.


Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.


At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F
At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.


I have gotten through the sysgen stage with no problems.


Thanks the interesting diversion, everyone.


Mark Gutzwiller

---In hercules-***@yahoogroups.com, <***@...> wrote :

Hi Folks:

Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.


I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.


Redoing 04 or 06 after getting the CMDREJ on 01F is fine...


The compression is optional.....


I will take a look at migrate03.


I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.


Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.


Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.


All comments are welcome...and greatly appreciated.


I second Mark's "Good Luck," and offer "Have Fun!"


Best Regards,
Steve Orso

[[e-mail] [hercules-390]]

---In hercules-***@yahoogroups.com, <***@...> wrote :

> I disagree with Paul, though, about using
> "/" for the command prefix. I think the "\"
> catches your eye better. It stands out
> from the slashes used in the job streams
> and directory paths.

Well, as far as I know, "/" is pretty much
universal. I can't remember if TK3 used
it first, which triggered my use, but
certainly in MVS/380, VM/380 and VSE/380
"/" is used exclusively.

So you will be making DOS/360 the only
user I know of that is using "\".

I'm not sure what Juergen used in TK4-,
but if he used "\", then fine, follow him,
since TK4- is one of the most important
distributions.

Also, using "/" in terminal commands has
nothing to do with directory names. MVS,
VM and DOS do not use PC filenames
so the "/" does not conflict even visually.

BFN. Paul.

[[e-mail] [hercules-390]]

- - - In hercules-***@yahoogroups.com, <***@...> wrote:
- - - beginning snipped - - -
> Also, using "/" in terminal commands has
>nothing to do with directory names. MVS,
>VM and DOS do not use PC filenames
>so the "/" does not conflict even visually.
> BFN. Paul.

Slash is also used in zOS SDSF to enter zOS commands.

So from a TK3 option to the zOS default code from IBM,
slash is what people are accustomed to.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Ok, Gang – I’m about to start the MIGRATE phase. Given how I get confused over integrated console responses, I feel I should clarify the following, which is found at the end of Steve’s writeup for MIGRATE01:

“ And when you do put more cards in the reader, you'll need to press Return in the Telnet window to simulate an Enter key for DOS. “

Does this mean responding with \[Enter] ? In other words, slash followed by pressing the Enter key?

Thanks!


From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 2:53 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Stephen,

I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.

Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.

At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F
At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.

I have gotten through the sysgen stage with no problems.

Thanks the interesting diversion, everyone.

Mark Gutzwiller

---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
Hi Folks:

Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.

I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.

Redoing 04 or 06 after getting the CMDREJ on 01F is fine...

The compression is optional.....

I will take a look at migrate03.

I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.

Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.

Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.

All comments are welcome...and greatly appreciated.

I second Mark's "Good Luck," and offer "Have Fun!"

Best Regards,
Steve Orso

[[e-mail] [hercules-390]]

I'm pretty sure that is correct.

That is exactly how to do an "enter"
at a terminal when using the
integrated console. I needed to do
that myself in various scripts.

BFN. Paul.




---In hercules-***@yahoogroups.com, <***@...> wrote :

Ok, Gang – I’m about to start the MIGRATE phase. Given how I get confused over integrated console responses, I feel I should clarify the following, which is found at the end of Steve’s writeup for MIGRATE01:

“ And when you do put more cards in the reader, you'll need to press Return in the Telnet window to simulate an Enter key for DOS. “

Does this mean responding with \[Enter] ? In other words, slash followed by pressing the Enter key?

Thanks!


From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 2:53 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07




Stephen,


I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.



Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.



At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F

At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.


I have gotten through the sysgen stage with no problems.



Thanks the interesting diversion, everyone.



Mark Gutzwiller


---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@...> wrote :
Hi Folks:


Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.



I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.



Redoing 04 or 06 after getting the CMDREJ on 01F is fine...



The compression is optional.....



I will take a look at migrate03.



I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.



Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.



Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.



All comments are welcome...and greatly appreciated.



I second Mark's "Good Luck," and offer "Have Fun!"



Best Regards,

Steve Orso

[[e-mail] [hercules-390]]

Ok, Thanks – here goes!

Sent from my Windows 10 phone

From: ***@yahoo.com.au [hercules-390]
Sent: Thursday, December 15, 2016 7:05 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
I'm pretty sure that is correct.

That is exactly how to do an "enter"
at a terminal when using the
integrated console. I needed to do
that myself in various scripts.

BFN. Paul.

---In hercules-***@yahoogroups.com, <***@...> wrote :

Ok, Gang – I’m about to start the MIGRATE phase. Given how I get confused over integrated console responses, I feel I should clarify the following, which is found at the end of Steve’s writeup for MIGRATE01:

“ And when you do put more cards in the reader, you'll need to press Return in the Telnet window to simulate an Enter key for DOS. “

Does this mean responding with \[Enter] ? In other words, slash followed by pressing the Enter key?

Thanks!


From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 2:53 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

Stephen,


I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.

Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.

At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F

At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.


I have gotten through the sysgen stage with no problems.

Thanks the interesting diversion, everyone.

Mark Gutzwiller

---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@...> wrote :
Hi Folks:


Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.

I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.

Redoing 04 or 06 after getting the CMDREJ on 01F is fine...

The compression is optional.....

I will take a look at migrate03.

I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.

Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.

Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.

All comments are welcome...and greatly appreciated.

I second Mark's "Good Luck," and offer "Have Fun!"

Best Regards,

Steve Orso




[Non-text portions of this message have been removed]

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

I’ve made it to the first stage of MIGRATE03, and immediately upon the first ipl 190 encountered the CMDREJ error:

HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6 +
PSW=00040005 C0003044 INST=D2FFB000F9BA MVC 0(256,11),2490(15) move_character
R:001FFFBD:K:06=000000 00000000 00000000 00000000 00 ................
R:000039BC:K:06=00000000 00000000 00000000 00000000 ................
GR00=000000FF GR01=00003088 GR02=00001050 GR03=9C002550
GR04=0000108A GR05=00000000 GR06=00000003 GR07=AC0022A0
GR08=8C00201E GR09=9C002D5A GR10=000024D8 GR11=001FFFBD
GR12=000027F8 GR13=000037F8 GR14=000001C0 GR15=40003002
HHCCP048I 001F:CCW=02002F9A 00000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E40 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
HHCCP014I CPU0000: Operation exception CODE=0001 ILC=2
PSW=FF050001 60002A64 INST=0000 ????? , ?
GR00=00002800 GR01=00002E0C GR02=00001038 GR03=000010A6
GR04=00000000 GR05=00001031 GR06=90002938 GR07=00001800
GR08=000001C0 GR09=8000280E GR10=00000190 GR11=001FFFFF
GR12=00001A60 GR13=000030E0 GR14=0000280A GR15=60003082
Command ==>

Do I enter a STOPALL and retry the ill?

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 7:05 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


I'm pretty sure that is correct.

That is exactly how to do an "enter"
at a terminal when using the
integrated console. I needed to do
that myself in various scripts.

BFN. Paul.

---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :

Ok, Gang – I’m about to start the MIGRATE phase. Given how I get confused over integrated console responses, I feel I should clarify the following, which is found at the end of Steve’s writeup for MIGRATE01:

“ And when you do put more cards in the reader, you'll need to press Return in the Telnet window to simulate an Enter key for DOS. “

Does this mean responding with \[Enter] ? In other words, slash followed by pressing the Enter key?

Thanks!


From: hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 2:53 AM
To: hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com>
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

Stephen,


I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.

Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.

At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F

At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.


I have gotten through the sysgen stage with no problems.

Thanks the interesting diversion, everyone.

Mark Gutzwiller

---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> mailto:hercules-***@yahoogroups.com, <***@... mailto:***@... <mailto:***@...%20mailto:***@...> > wrote :
Hi Folks:


Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.

I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.

Redoing 04 or 06 after getting the CMDREJ on 01F is fine...

The compression is optional.....

I will take a look at migrate03.

I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.

Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.

Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.

All comments are welcome...and greatly appreciated.

I second Mark's "Good Luck," and offer "Have Fun!"

Best Regards,

Steve Orso

[[e-mail] [hercules-390]]

Michael,


Go ahead and re-run that step.




---In hercules-***@yahoogroups.com, <***@...> wrote :

I’ve made it to the first stage of MIGRATE03, and immediately upon the first ipl 190 encountered the CMDREJ error:

[[e-mail] [hercules-390]]

Ok, for the record, I repeated the ipl 190.

Got “HHCPN053E ipl rejected: All CPU’s must be stopped”

Did STOPALL and re-did ipl 190

Seems to have worked.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Thursday, December 15, 2016 8:45 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 

Michael,

Go ahead and re-run that step.



---In hercules-***@yahoogroups.com, <***@...> wrote :
I’ve made it to the first stage of MIGRATE03, and immediately upon the first ipl 190 encountered the CMDREJ error:
  




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

---In hercules-***@yahoogroups.com, <***@...> wrote :

> Ok, for the record, I repeated the ipl 190.
> Got “HHCPN053E ipl rejected: All CPU’s must be stopped”
> Did STOPALL and re-did ipl 190
> Seems to have worked.

If simply re-ipling fixes the problem, then
check to see if a "pause 2" before the
IPL also fixes the problem.

Or if that doesn't work, then try doing:

ipl 190
pause 2
stopall
ipl 190

and see if you get consistent results when
you rerun from the top.

BFN. Paul.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Success! (I think). Got all the way through MIGRATE phase tonight. Thanks again to everyone, including Mark, Paul, and Steve!

Now to read ahead to what’s next!


From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 8:45 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07



Michael,

Go ahead and re-run that step.



---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :
I’ve made it to the first stage of MIGRATE03, and immediately upon the first ipl 190 encountered the CMDREJ error:

[[e-mail] [hercules-390]]

I suggest:

1. Post the (hopefully automated) script you
are running so that we can see if we can
spot anything.

2. Try adding in some "pause" statements.

3. Have the whole process done automatically
so that whenever you want to experiment with
a changed pause number of anything else,
you just type in "doit" and wait a couple of
minutes to see the result.

BFN. Paul.




---In hercules-***@yahoogroups.com, <***@...> wrote :

I’ve made it to the first stage of MIGRATE03, and immediately upon the first ipl 190 encountered the CMDREJ error:

HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6 +
PSW=00040005 C0003044 INST=D2FFB000F9BA MVC 0(256,11),2490(15) move_character
R:001FFFBD:K:06=000000 00000000 00000000 00000000 00 ................
R:000039BC:K:06=00000000 00000000 00000000 00000000 ................
GR00=000000FF GR01=00003088 GR02=00001050 GR03=9C002550
GR04=0000108A GR05=00000000 GR06=00000003 GR07=AC0022A0
GR08=8C00201E GR09=9C002D5A GR10=000024D8 GR11=001FFFBD
GR12=000027F8 GR13=000037F8 GR14=000001C0 GR15=40003002
HHCCP048I 001F:CCW=02002F9A 00000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E40 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
HHCCP014I CPU0000: Operation exception CODE=0001 ILC=2
PSW=FF050001 60002A64 INST=0000 ????? , ?
GR00=00002800 GR01=00002E0C GR02=00001038 GR03=000010A6
GR04=00000000 GR05=00001031 GR06=90002938 GR07=00001800
GR08=000001C0 GR09=8000280E GR10=00000190 GR11=001FFFFF
GR12=00001A60 GR13=000030E0 GR14=0000280A GR15=60003082
Command ==>

Do I enter a STOPALL and retry the ill?

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 7:05 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07




I'm pretty sure that is correct.

That is exactly how to do an "enter"
at a terminal when using the
integrated console. I needed to do
that myself in various scripts.

BFN. Paul.

---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@...> wrote :

Ok, Gang – I’m about to start the MIGRATE phase. Given how I get confused over integrated console responses, I feel I should clarify the following, which is found at the end of Steve’s writeup for MIGRATE01:

“ And when you do put more cards in the reader, you'll need to press Return in the Telnet window to simulate an Enter key for DOS. “

Does this mean responding with \[Enter] ? In other words, slash followed by pressing the Enter key?

Thanks!


From: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com]
Sent: Thursday, December 15, 2016 2:53 AM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

Stephen,


I don't have many notes, but perhaps show examples of expected Hercules errors during the IPL, and unexpected ones.

Show the lines from the dos360.cnf that need to be changed to use the integrated console. I disagree with Paul, though, about using "/" for the command prefix. I think the "\" catches your eye better. It stands out from the slashes used in the job streams and directory paths.

At the end of MIGRATE02, there is this message: HHC1C001A Enter input for console device 001F

At the MIGRATE03 IPL, there is the "CMD REJ", following the current instructions.


I have gotten through the sysgen stage with no problems.

Thanks the interesting diversion, everyone.

Mark Gutzwiller

---In hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com, <***@... mailto:***@... mailto:***@...%20mailto:***@...> wrote :
Hi Folks:


Many thanks for continuing this conversation while I was out of the loop. And yes, great news, Michael. Congratulations on getting to distrib09.

I have seen 260F etc. when running the integrated console....and Mark is right, 3008 is the gold standard for successful completion of the restore..provided the record counts match.

Redoing 04 or 06 after getting the CMDREJ on 01F is fine...

The compression is optional.....

I will take a look at migrate03.

I had a retired NT machine that provided a working telnet, and all of my examples on the web site are based on that working telnet. It is clear that the Hercules Integrated Console creates some differences that my instructions do not account for, and I am very grateful that all of you are pursuing this.

Given the state of telnet support in 3.07 and 3.12, I must update my site....and I will.

Mark, if you have notes about your experiences that have not yet been posted, please feel free to share them. I welcome critique, and the 75+ posts to this thread will be the basis for improvements to the DOS/360 site.

All comments are welcome...and greatly appreciated.

I second Mark's "Good Luck," and offer "Have Fun!"

Best Regards,

Steve Orso

[[e-mail] [hercules-390]]

Ok, will do.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Wednesday, December 14, 2016 8:25 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
It's safe to run Distrib06 again. It initalizes a different dasd.

Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :
Ok, just ran script distrib06.  This ended with “CMDREJ”:
 
script rc/distrib06.rc
# DISTRIB06 Initialize 2314 DOSRES on 190
stopall
devinit 280 tape/k360n-ma108a.aws ro
HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
HHCTA066I 0280: option 'ro' accepted.
HHCPN098I Device 0:0280 initialized
iplc 280
devinit 00c jcl/distrib06.jcl
HHCPN098I Device 0:000C initialized
HHCPN013I EOF reached on SCRIPT file. Processing complete.
HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
PSW=00000005 C0000020 INST=D2FF11570156 MVC   343(256,1),342(0)      move_character
R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
GR00=00000000  GR01=001FFE00  GR02=00000000  GR03=00000000
GR04=00000000  GR05=00000000  GR06=00000000  GR07=00000000
GR08=00000000  GR09=00000000  GR10=00000000  GR11=00000000
GR12=00000000  GR13=00000000  GR14=00000000  GR15=00000000
HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000 00000000 ................
HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000 00000000 ................
HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
HHCCP077I 001F:Sense=CMDREJ
Command ==>
 
What should I do next?
 
 
 
 
From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 7:46 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
 
 
Just run distrib04 script now. That just initializes the DASD for the next step, so distrib04 can be re-run, if needed, without having to start at the beginning.
 
Mark Gutzwiller
 


---In hercules-***@yahoogroups.com, <***@...> wrote :
Ok, but – sitting at this point – should I enter \22 and “ext” before proceeding to distrib04? Or, just run the distrib04 script now?

Sent from my Windows 10 phone




[Non-text portions of this message have been removed]

[Mike Stramba [e-mail] [hercules-390]]

On 12/14/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at
> the tail end of DISTRIB03. The web writeup lists the following console
> output:
>
> 3008
> 0280
> 2E0F
> 4022A
>
> My hercules console output shows:
>
> 3008
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> .

Did you get the :
3007
END OF JOB

preceeding the 3008 message ?

I would think that the END OF JOB is the critical message as per Steve's note :

"When you see 3007, END OF JOB, and 3008 on the telnet console, the
restore is complete. "

If so, then I think you're good to proceed.

You could also run a dasdls on res11a, res11b to see if the files are
there (here's mine) :

Did you try running dasdls on your failing 132 - res11c ?

Mike

p.s. Do you have any reason for running hercules 3.07 ? I don't
think that's the problem, but I installed using Hercules 3.12 with no
telnet errors.

Mike

C:\hercules\dos\dos360\r\dasd>dasdls res11a.2311
res11a.2311: VOLSER=RES11A
DOS.SYSRES.FILE.VOLUME.1

C:\hercules\dos\dos360\r\dasd>dasdls res11b.2311
res11b.2311: VOLSER=RES11B
DOS.SYSRES.FILE.VOLUME.2

[[e-mail] [hercules-390]]

Mike, When I try to run dasdls res11a.2311 it says “...not recognized as internal or eternal command.”


Sent from my Windows 10 phone

From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Wednesday, December 14, 2016 7:18 PM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
On 12/14/16, ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at
> the tail end of DISTRIB03. The web writeup lists the following console
> output:
>
> 3008
> 0280
> 2E0F
> 4022A
>
> My hercules console output shows:
>
> 3008
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> .

Did you get the :
3007
END OF JOB

preceeding the 3008 message ?

I would think that the END OF JOB is the critical message as per Steve's note :

"When you see 3007, END OF JOB, and 3008 on the telnet console, the
restore is complete. "

If so, then I think you're good to proceed.

You could also run a dasdls on res11a, res11b to see if the files are
there (here's mine) :

Did you try running dasdls on your failing 132 - res11c ?

Mike

p.s. Do you have any reason for running hercules 3.07 ? I don't
think that's the problem, but I installed using Hercules 3.12 with no
telnet errors.

Mike

C:\hercules\dos\dos360\r\dasd>dasdls res11a.2311
res11a.2311: VOLSER=RES11A
DOS.SYSRES.FILE.VOLUME.1

C:\hercules\dos\dos360\r\dasd>dasdls res11b.2311
res11b.2311: VOLSER=RES11B
DOS.SYSRES.FILE.VOLUME.2




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

You should have a "dasdls" command as
part of Hercules, like this:

C:\herc380>dir dasdls.exe
Volume in drive C is OS
Volume Serial Number is DE22-8195

Directory of C:\herc380

2016-12-07 12:44 14,848 dasdls.exe
1 File(s) 14,848 bytes
0 Dir(s) 27,828,137,984 bytes free



Go to c:\ and do "dir dasdls.exe /s" and it
should find where you installed Hercules.
Then you can either add that location to
your path, or execute it directly, e.g.

\herc312\dasdls

BFN. Paul.



P.S. I was going to make a joke about an
"eternal command", but couldn't remember
any funny command in the 10 commandments,
like "thou shalt not practice witchcraft".



---In hercules-***@yahoogroups.com, <***@...> wrote :

Mike, When I try to run dasdls res11a.2311 it says “...not recognized as internal or eternal command.”


Sent from my Windows 10 phone

From: Mike Stramba ***@... mailto:***@... [hercules-390]
Sent: Wednesday, December 14, 2016 7:18 PM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


On 12/14/16, ***@... mailto:***@... [hercules-390]
<hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com> wrote:
> Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at
> the tail end of DISTRIB03. The web writeup lists the following console
> output:
>
> 3008
> 0280
> 2E0F
> 4022A
>
> My hercules console output shows:
>
> 3008
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> .

Did you get the :
3007
END OF JOB

preceeding the 3008 message ?

I would think that the END OF JOB is the critical message as per Steve's note :

"When you see 3007, END OF JOB, and 3008 on the telnet console, the
restore is complete. "

If so, then I think you're good to proceed.

You could also run a dasdls on res11a, res11b to see if the files are
there (here's mine) :

Did you try running dasdls on your failing 132 - res11c ?

Mike

p.s. Do you have any reason for running hercules 3.07 ? I don't
think that's the problem, but I installed using Hercules 3.12 with no
telnet errors.

Mike

C:\hercules\dos\dos360\r\dasd>dasdls res11a.2311
res11a.2311: VOLSER=RES11A
DOS.SYSRES.FILE.VOLUME.1

C:\hercules\dos\dos360\r\dasd>dasdls res11b.2311
res11b.2311: VOLSER=RES11B
DOS.SYSRES.FILE.VOLUME.2




[Non-text portions of this message have been removed]

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Ok, got it:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>hercCD

C:\WINDOWS\system32>CD C:\Program Files\Hercules\Hercules 3.07 (32 Bit)\

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/res11a.2311
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/res11a.2311: VOLSER=RES11A
DOS.SYSRES.FILE.VOLUME.1

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
HHCDU009E Cannot open dasd/: No such file or directory

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/res11b.2311
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/res11b.2311: VOLSER=RES11B
DOS.SYSRES.FILE.VOLUME.2

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/res11c.2311
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/res11c.2311: VOLSER=RES11C
DOS.SYSRES.FILE.VOLUME.3
DOS.SYSRLB.FILE.VOLUME.3
DOS.SYSSLB.FILE.VOLUME.3

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/wrk14a.2314
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/wrk14a.2314: VOLSER=WRK14A

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/wrk14b.2314
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/wrk14b.2314: VOLSER=WRK14B

C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>dasdls dasd/dosres.2314
Hercules DASD list program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
dasd/dosres.2314: VOLSER=DOSRES




C:\Program Files\Hercules\Hercules 3.07 (32 Bit)>From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Wednesday, December 14, 2016 8:49 PM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


You should have a "dasdls" command as
part of Hercules, like this:

C:\herc380>dir dasdls.exe
Volume in drive C is OS
Volume Serial Number is DE22-8195

Directory of C:\herc380

2016-12-07 12:44 14,848 dasdls.exe
1 File(s) 14,848 bytes
0 Dir(s) 27,828,137,984 bytes free

Go to c:\ and do "dir dasdls.exe /s" and it
should find where you installed Hercules.
Then you can either add that location to
your path, or execute it directly, e.g.

\herc312\dasdls

BFN. Paul.

P.S. I was going to make a joke about an
"eternal command", but couldn't remember
any funny command in the 10 commandments,
like "thou shalt not practice witchcraft".

---In hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> , <***@... <mailto:***@...> > wrote :

Mike, When I try to run dasdls res11a.2311 it says “...not recognized as internal or eternal command.”


Sent from my Windows 10 phone

From: Mike Stramba ***@... mailto:***@... [hercules-390]
Sent: Wednesday, December 14, 2016 7:18 PM
To: hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com> mailto:hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


On 12/14/16, ***@... mailto:***@... [hercules-390]
<hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com <mailto:hercules-***@yahoogroups.com%20mailto:hercules-***@yahoogroups.com> > wrote:
> Ok Gang, I am slowly stepping through this in a deliberate manner. I’m at
> the tail end of DISTRIB03. The web writeup lists the following console
> output:
>
> 3008
> 0280
> 2E0F
> 4022A
>
> My hercules console output shows:
>
> 3008
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> .

Did you get the :
3007
END OF JOB

preceeding the 3008 message ?

I would think that the END OF JOB is the critical message as per Steve's note :

"When you see 3007, END OF JOB, and 3008 on the telnet console, the
restore is complete. "

If so, then I think you're good to proceed.

You could also run a dasdls on res11a, res11b to see if the files are
there (here's mine) :

Did you try running dasdls on your failing 132 - res11c ?

Mike

p.s. Do you have any reason for running hercules 3.07 ? I don't
think that's the problem, but I installed using Hercules 3.12 with no
telnet errors.

Mike

C:\hercules\dos\dos360\r\dasd>dasdls res11a.2311
res11a.2311: VOLSER=RES11A
DOS.SYSRES.FILE.VOLUME.1

C:\hercules\dos\dos360\r\dasd>dasdls res11b.2311
res11b.2311: VOLSER=RES11B
DOS.SYSRES.FILE.VOLUME.2




[Non-text portions of this message have been removed]

[Mike Stramba [e-mail] [hercules-390]]

On 12/12/16, ***@yahoo.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> In both steps, the tapes are mounted right before IPL. I wonder if Hercules
> is still mounting the tapes when it tries to IPL?
> I wonder if a "stopall" should be added after the devinit as a delay?

stopall stops all the (virtual/Hercules) CPUS.

It has nothing to do with script processing / delays, which is a host OS issue.

scripts, sh, devinit, are "meta" commands that can be executed
whether the hercules cpu's are running or not.

Mike

[[e-mail] [hercules-390]]

Well, I tried it anyway, before I saw your response. The as result was just as you said. No difference. I also tried to use "Pause 5" after the devinit, and that also didn't work.


I put "Sysclear" after the "stopall" in distrib04.cnf, and the script ran fine.


Mark Gutzwiller

[[e-mail] [hercules-390]]

This is starting to feel a little odd. Presumably these scripts have been executed many times in the past 
 wonder why they’re burping now? Has 3.07 been updated recently?

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Tuesday, December 13, 2016 11:29 AM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Well, I tried it anyway, before I saw your response. The as result was just as you said. No difference.
I also tried to use "Pause 5" after the devinit, and that also didn't work.

I put "Sysclear" after the "stopall" in distrib04.cnf, and the script ran fine.

Mark Gutzwiller




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

I downloaded the DOS360.zip just last month, and going from the dates in the zip file, it's been almost a year.

I guess most people are more interested in MVS or VM/370 than any DOS. You may have been the first one to try it out.


Mark Gutzwiller


---In hercules-***@yahoogroups.com, <***@...> wrote :

This is starting to feel a little odd. Presumably these scripts have been executed many times in the past 
 wonder why they’re burping now? Has 3.07 been updated recently?

Sent from my Windows 10 phone

From: ***@... mailto:***@... [hercules-390]
Sent: Tuesday, December 13, 2016 11:29 AM
To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Well, I tried it anyway, before I saw your response. The as result was just as you said. No difference.
I also tried to use "Pause 5" after the devinit, and that also didn't work.

I put "Sysclear" after the "stopall" in distrib04.cnf, and the script ran fine.

Mark Gutzwiller




[Non-text portions of this message have been removed]

[Mike Stramba [e-mail] [hercules-390]]

Ok, I got "sucked" in and had to try the install :/

Are these "4307A" message, the dos360 version of windows "Are you sure?"

I tried to automate the "ext" responses using the i/o stat messages
from "+1F", but it seemed to "run away" out of control ;). So back
to the manual method

If so, are they "hard coded" in the install tapes ?

Quite annoying ... though I guess just another anachronism of dos-50 yrs ago :/

Mike

On 12/13/16, ***@yahoo.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> I downloaded the DOS360.zip just last month, and going from the dates in the
> zip file, it's been almost a year.
>
> I guess most people are more interested in MVS or VM/370 than any DOS. You
> may have been the first one to try it out.
>
>
> Mark Gutzwiller
>
>
> ---In hercules-***@yahoogroups.com, <***@...> wrote :
>
> This is starting to feel a little odd. Presumably these scripts have been
> executed many times in the past 
 wonder why they’re burping now? Has 3.07
> been updated recently?
>
> Sent from my Windows 10 phone
>
> From: ***@... mailto:***@... [hercules-390]
> Sent: Tuesday, December 13, 2016 11:29 AM
> To: hercules-***@yahoogroups.com mailto:hercules-***@yahoogroups.com
> Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
>
>
> Well, I tried it anyway, before I saw your response. The as result was just
> as you said. No difference.
> I also tried to use "Pause 5" after the devinit, and that also didn't
> work.
>
> I put "Sysclear" after the "stopall" in distrib04.cnf, and the script ran
> fine.
>
> Mark Gutzwiller
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>

[[e-mail] [hercules-390]]

I thought i had replied to this twice, but it's not showing ... so here goes again: Can I just rerun distrib04 and distrib06 or do I need to redo al steps from the beginning?

[[e-mail] [hercules-390]]

I don't know. I never tried that. I just restarted at the distrib01 stage. But it looks like if you could rerun distrib04 (initialize res11C), distrib05 (restore res11c), and distrib06 (initialize DOSRES) without a problem.



Mark Gutzwiller.

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Sooo, can I just rerun those two scripts or do I need to restart from the beginning?

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Monday, December 12, 2016 7:12 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Okay, after trying it several times, it looks like, for some reason, steps distrib04 and distrib06 need to be done twice. I receive errors the first time each one is run, but the second time for each they run okay. EOJ is printed for both..

After finishing all the distrib stages, I can IPL 132 okay (migrate01 stage).


Mark Gutzwiller

---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi Folks,

I feel like I’m back to the original obstacle; namely, the inability to IPL when starting the MIGRATE phase. I’m pretty sure I’ve entered the commands exactly as for MIGRATE01.

[[e-mail] [hercules-390]]

Sooo, can I just rerun those two scripts or do i need to rerun everything from the beginning?

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Monday, December 12, 2016 7:11 PM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Okay, after trying it several times, it looks like, for some reason, steps distrib04 and distrib06 need to be done twice. I receive errors the first time each one is run, but the second time for each they run okay. EOJ is printed for both..

After finishing all the distrib stages, I can IPL 132 okay (migrate01 stage).


Mark Gutzwiller

---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi Folks,
 
I feel like I’m back to the original obstacle; namely, the inability to IPL when starting the MIGRATE phase.  I’m pretty sure I’ve entered the commands exactly as  for MIGRATE01. 
 





[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Hi Michael:


I have been able to reproduce the issue you experience on Hercules 3.07, 3.12, and 4.0, all 64-bit on Windows.


I believe the difficulty arrises because of a command reject on the console at the beginning of the distrib04.rc (initialize res11c) step. When the initialize fails, the restore fails, and the subsequent IPL of 132 will also fail.


Please take a look at console log in my reproduction of the issue to confirm you are experiencing what I have describet.


10:54:02 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
10:54:02 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6 00090000 0000024425.F....
10:54:02 HHCCP075I 0280:Stat=2600 Count=0001
10:54:02 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF FF000000
10:54:02 HHCCP077I 0280:Sense=INTREQ EOC WRI
10:54:02 0280
10:54:02 260F
10:54:02 4002A
10:54:02 HHC1C001A Enter input for console device 001F


4002A is the code for the completion of the restore that is in distrib.rc. Notice message HHC1C001A: the restore application has issued a read to the console. Now start distrib04.rc.


10:54:15 script rc/distrib04.rc
10:54:15 # DISTRIB04 Initialize 2311 RES11C on 132
10:54:15 stopall
10:54:15 devinit 281 tape/k360n-ma110a.aws ro
10:54:15 HHCTA004I 0281: tape/k360n-ma110a.aws is a AWS Format tape file
10:54:15 HHCTA066I 0281: option 'ro' accepted.
10:54:15 HHCPN098I Device 0:0281 initialized
10:54:15 iplc 281
10:54:15 devinit 00c jcl/distrib04.jcl
10:54:15 HHCPN098I Device 0:000C initialized
10:54:15 HHCPN013I EOF reached on SCRIPT file. Processing complete.
10:54:15 HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
10:54:15 PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0) move_character
10:54:15 R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
10:54:15 R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
10:54:15 GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
10:54:15 GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
10:54:15 GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
10:54:15 GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000


The above addressing exception is normal and expected; the initialize program is determining the amount of memory installed. GR01 is very close to the 2MB line. The next message is much more interesting. It is a command reject by the console at X'01F'.


10:54:15 HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000 00000000 ................
10:54:15 HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000 00000000 ................
10:54:15 HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000 00000000
10:54:15 HHCCP077I 001F:Sense=CMDREJ


At this point, the initialize program has gone comatose. Initialize fails, and so the restore fails, and then the IPL 132 fails.


There seem to be two workarounds.


1) When you get the command reject message, repeat at that point the step that you were attempting. I expect you will need to repeat 04 and 06.


2) When distrib03 (and 05) completes, type \ and enter before starting the next script to clear the outstanding read.


Let me know how you make out. I will do some other tests and revise the web site based on your feedback and the additional testing.


Best Regards,
Steve Orso

['MICHAEL (iCloud)' [e-mail] [hercules-390]]

Well, I went back and reran 04, 05, 06 - got the CMDREJ after 06. Reran
06 and it worked. Went on to MIGRATE01. Entered STOPALL and SYSCLEAR
right before the 'ipl 132' but then ran into the same "IPL Failed" problem.


Here's the console:

stopall
+
devinit 280 tape/k360n-ma108a.aws ro
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
HHCTA066I 0280: option 'ro' accepted.
HHCPN098I Device 0:0280 initialized
iplc 280
devinit 00c jcl/distrib06.jcl
HHCPN098I Device 0:000C initialized
HHCPN013I EOF reached on SCRIPT file. Processing complete.
HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
move_character
R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
CONTROL CARD ANALYSIS AND LABEL CHECKING
UTILITY MODIFIER CARD
// UID IR,C1
SURFACE ANALYSIS AND HA-R0 GENERATION
SYSOPT
LAB CYL CREATION
SYSOPT
// VTOC STRTADR=(0199010),EXTENT=(10)
VOL1DOSRES
EOJ
stoo
HHCPN139E Command "stoo" not found; enter '?' for list.
stop
stopall
sysclear
devinit 00e prt/migrate-1-unloadlivs.txt crlf
HHCPN098I Device 0:000E initialized
sh hetinit -d -n tape/migrate-libs.aws
Hercules HET IEHINITT program Version 3.07
(c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
devinit 280 tape/migrate-libs.aws
HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
HHCTA004I 0280: tape/migrate-libs.aws is a AWS Format tape file
HHCPN098I Device 0:0280 initialized
stopall
sysclear
ipl 132
HHCCP029E S/370 mode IPL failed: CSW status=0E00
Sense=000800C8 0000

__________________________________

From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
Sent: Tuesday, December 13, 2016 11:52 AM
To: hercules-***@yahoogroups.com
Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07


Hi Michael:

I have been able to reproduce the issue you experience on Hercules 3.07,
3.12, and 4.0, all 64-bit on Windows.

I believe the difficulty arrises because of a command reject on the console
at the beginning of the distrib04.rc (initialize res11c) step. When the
initialize fails, the restore fails, and the subsequent IPL of 132 will also
fail.

Please take a look at console log in my reproduction of the issue to confirm
you are experiencing what I have describet.

10:54:02 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
10:54:02 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6
00090000 0000024425.F....
10:54:02 HHCCP075I 0280:Stat=2600 Count=0001
10:54:02 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF
FF000000
10:54:02 HHCCP077I 0280:Sense=INTREQ EOC WRI
10:54:02 0280
10:54:02 260F
10:54:02 4002A
10:54:02 HHC1C001A Enter input for console device 001F

4002A is the code for the completion of the restore that is in distrib.rc.
Notice message HHC1C001A: the restore application has issued a read to the
console. Now start distrib04.rc.

10:54:15 script rc/distrib04.rc
10:54:15 # DISTRIB04 Initialize 2311 RES11C on 132
10:54:15 stopall
10:54:15 devinit 281 tape/k360n-ma110a.aws ro
10:54:15 HHCTA004I 0281: tape/k360n-ma110a.aws is a AWS Format tape file
10:54:15 HHCTA066I 0281: option 'ro' accepted.
10:54:15 HHCPN098I Device 0:0281 initialized
10:54:15 iplc 281
10:54:15 devinit 00c jcl/distrib04.jcl
10:54:15 HHCPN098I Device 0:000C initialized
10:54:15 HHCPN013I EOF reached on SCRIPT file. Processing complete.
10:54:15 HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
10:54:15 PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
move_character
10:54:15 R:001FFF57:K:06=00 00000000 00000000 00000000 000000
................
10:54:15 R:00000156:K:06=0000 00000000 00000000 00000000 0000
................
10:54:15 GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
10:54:15 GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
10:54:15 GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
10:54:15 GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000

The above addressing exception is normal and expected; the initialize
program is determining the amount of memory installed. GR01 is very close
to the 2MB line. The next message is much more interesting. It is a
command reject by the console at X'01F'.

10:54:15 HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000
00000000 ................
10:54:15 HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000
00000000 ................
10:54:15 HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000
00000000
10:54:15 HHCCP077I 001F:Sense=CMDREJ

At this point, the initialize program has gone comatose. Initialize fails,
and so the restore fails, and then the IPL 132 fails.

There seem to be two workarounds.

1) When you get the command reject message, repeat at that point the step
that you were attempting. I expect you will need to repeat 04 and 06.

2) When distrib03 (and 05) completes, type \ and enter before starting the
next script to clear the outstanding read.

Let me know how you make out. I will do some other tests and revise the web
site based on your feedback and the additional testing.

Best Regards,
Steve Orso

[Mike Stramba [e-mail] [hercules-390]]

Sounds like maybe your distrib05 and/or your distrib04 didn't work.

Exit hercules, open a cmd prompt where your dasd is and run dasdls res11c.2311

Here's my output

res11c.2311: VOLSER=RES11C

DOS.SYSRES.FILE.VOLUME.3
DOS.SYSRLB.FILE.VOLUME.3
DOS.SYSSLB.FILE.VOLUME.3

Mike

On 12/13/16, 'MICHAEL (iCloud)' ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Well, I went back and reran 04, 05, 06 - got the CMDREJ after 06. Reran
> 06 and it worked. Went on to MIGRATE01. Entered STOPALL and SYSCLEAR
> right before the 'ipl 132' but then ran into the same "IPL Failed" problem.
>
>
> Here's the console:
>
> stopall
> +
> devinit 280 tape/k360n-ma108a.aws ro
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
> HHCTA066I 0280: option 'ro' accepted.
> HHCPN098I Device 0:0280 initialized
> iplc 280
> devinit 00c jcl/distrib06.jcl
> HHCPN098I Device 0:000C initialized
> HHCPN013I EOF reached on SCRIPT file. Processing complete.
> HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
> PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
> move_character
> R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
> R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
> GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
> GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
> GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
> GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
> CONTROL CARD ANALYSIS AND LABEL CHECKING
> UTILITY MODIFIER CARD
> // UID IR,C1
> SURFACE ANALYSIS AND HA-R0 GENERATION
> SYSOPT
> LAB CYL CREATION
> SYSOPT
> // VTOC STRTADR=(0199010),EXTENT=(10)
> VOL1DOSRES
> EOJ
> stoo
> HHCPN139E Command "stoo" not found; enter '?' for list.
> stop
> stopall
> sysclear
> devinit 00e prt/migrate-1-unloadlivs.txt crlf
> HHCPN098I Device 0:000E initialized
> sh hetinit -d -n tape/migrate-libs.aws
> Hercules HET IEHINITT program Version 3.07
> (c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
> devinit 280 tape/migrate-libs.aws
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> HHCTA004I 0280: tape/migrate-libs.aws is a AWS Format tape file
> HHCPN098I Device 0:0280 initialized
> stopall
> sysclear
> ipl 132
> HHCCP029E S/370 mode IPL failed: CSW status=0E00
> Sense=000800C8 0000
>
> __________________________________
>
> From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
> Sent: Tuesday, December 13, 2016 11:52 AM
> To: hercules-***@yahoogroups.com
> Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
>
>
> Hi Michael:
>
> I have been able to reproduce the issue you experience on Hercules 3.07,
> 3.12, and 4.0, all 64-bit on Windows.
>
> I believe the difficulty arrises because of a command reject on the console
> at the beginning of the distrib04.rc (initialize res11c) step. When the
> initialize fails, the restore fails, and the subsequent IPL of 132 will
> also
> fail.
>
> Please take a look at console log in my reproduction of the issue to
> confirm
> you are experiencing what I have describet.
>
> 10:54:02 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> 10:54:02 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6
> 00090000 0000024425.F....
> 10:54:02 HHCCP075I 0280:Stat=2600 Count=0001
> 10:54:02 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF
> FF000000
> 10:54:02 HHCCP077I 0280:Sense=INTREQ EOC WRI
> 10:54:02 0280
> 10:54:02 260F
> 10:54:02 4002A
> 10:54:02 HHC1C001A Enter input for console device 001F
>
> 4002A is the code for the completion of the restore that is in distrib.rc.
> Notice message HHC1C001A: the restore application has issued a read to the
> console. Now start distrib04.rc.
>
> 10:54:15 script rc/distrib04.rc
> 10:54:15 # DISTRIB04 Initialize 2311 RES11C on 132
> 10:54:15 stopall
> 10:54:15 devinit 281 tape/k360n-ma110a.aws ro
> 10:54:15 HHCTA004I 0281: tape/k360n-ma110a.aws is a AWS Format tape file
> 10:54:15 HHCTA066I 0281: option 'ro' accepted.
> 10:54:15 HHCPN098I Device 0:0281 initialized
> 10:54:15 iplc 281
> 10:54:15 devinit 00c jcl/distrib04.jcl
> 10:54:15 HHCPN098I Device 0:000C initialized
> 10:54:15 HHCPN013I EOF reached on SCRIPT file. Processing complete.
> 10:54:15 HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
> 10:54:15 PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
> move_character
> 10:54:15 R:001FFF57:K:06=00 00000000 00000000 00000000 000000
> ................
> 10:54:15 R:00000156:K:06=0000 00000000 00000000 00000000 0000
> ................
> 10:54:15 GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
> 10:54:15 GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
> 10:54:15 GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
> 10:54:15 GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
>
> The above addressing exception is normal and expected; the initialize
> program is determining the amount of memory installed. GR01 is very close
> to the 2MB line. The next message is much more interesting. It is a
> command reject by the console at X'01F'.
>
> 10:54:15 HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000
> 00000000 ................
> 10:54:15 HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000
> 00000000 ................
> 10:54:15 HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000
> 00000000
> 10:54:15 HHCCP077I 001F:Sense=CMDREJ
>
> At this point, the initialize program has gone comatose. Initialize fails,
> and so the restore fails, and then the IPL 132 fails.
>
> There seem to be two workarounds.
>
> 1) When you get the command reject message, repeat at that point the step
> that you were attempting. I expect you will need to repeat 04 and 06.
>
> 2) When distrib03 (and 05) completes, type \ and enter before starting the
> next script to clear the outstanding read.
>
> Let me know how you make out. I will do some other tests and revise the
> web
> site based on your feedback and the additional testing.
>
> Best Regards,
> Steve Orso
>
>

[[e-mail] [hercules-390]]

Thanks, Mike. I’ll try this tomorrow.

Sent from my Windows 10 phone

From: Mike Stramba ***@gmail.com [hercules-390]
Sent: Tuesday, December 13, 2016 7:25 PM
To: hercules-***@yahoogroups.com
Subject: Re: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Sounds like maybe your distrib05 and/or your distrib04 didn't work.

Exit hercules, open a cmd prompt where your dasd is and run dasdls res11c.2311

Here's my output

res11c.2311: VOLSER=RES11C

DOS.SYSRES.FILE.VOLUME.3
DOS.SYSRLB.FILE.VOLUME.3
DOS.SYSSLB.FILE.VOLUME.3

Mike

On 12/13/16, 'MICHAEL (iCloud)' ***@mac.com [hercules-390]
<hercules-***@yahoogroups.com> wrote:
> Well, I went back and reran 04, 05, 06 - got the CMDREJ after 06. Reran
> 06 and it worked. Went on to MIGRATE01. Entered STOPALL and SYSCLEAR
> right before the 'ipl 132' but then ran into the same "IPL Failed" problem.
>
>
> Here's the console:
>
> stopall
> +
> devinit 280 tape/k360n-ma108a.aws ro
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> HHCTA004I 0280: tape/k360n-ma108a.aws is a AWS Format tape file
> HHCTA066I 0280: option 'ro' accepted.
> HHCPN098I Device 0:0280 initialized
> iplc 280
> devinit 00c jcl/distrib06.jcl
> HHCPN098I Device 0:000C initialized
> HHCPN013I EOF reached on SCRIPT file. Processing complete.
> HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
> PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
> move_character
> R:001FFF57:K:06=00 00000000 00000000 00000000 000000 ................
> R:00000156:K:06=0000 00000000 00000000 00000000 0000 ................
> GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
> GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
> GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
> GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
> CONTROL CARD ANALYSIS AND LABEL CHECKING
> UTILITY MODIFIER CARD
> // UID IR,C1
> SURFACE ANALYSIS AND HA-R0 GENERATION
> SYSOPT
> LAB CYL CREATION
> SYSOPT
> // VTOC STRTADR=(0199010),EXTENT=(10)
> VOL1DOSRES
> EOJ
> stoo
> HHCPN139E Command "stoo" not found; enter '?' for list.
> stop
> stopall
> sysclear
> devinit 00e prt/migrate-1-unloadlivs.txt crlf
> HHCPN098I Device 0:000E initialized
> sh hetinit -d -n tape/migrate-libs.aws
> Hercules HET IEHINITT program Version 3.07
> (c)Copyright 1999-2010 by Roger Bowler, Jan Jaeger, and others
> devinit 280 tape/migrate-libs.aws
> HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> HHCTA004I 0280: tape/migrate-libs.aws is a AWS Format tape file
> HHCPN098I Device 0:0280 initialized
> stopall
> sysclear
> ipl 132
> HHCCP029E S/370 mode IPL failed: CSW status=0E00
> Sense=000800C8 0000
>
> __________________________________
>
> From: hercules-***@yahoogroups.com [mailto:hercules-***@yahoogroups.com]
> Sent: Tuesday, December 13, 2016 11:52 AM
> To: hercules-***@yahoogroups.com
> Subject: RE: [hercules-390] Re: Can't IPL During Install of Hercules 3.07
>
>
> Hi Michael:
>
> I have been able to reproduce the issue you experience on Hercules 3.07,
> 3.12, and 4.0, all 64-bit on Windows.
>
> I believe the difficulty arrises because of a command reject on the console
> at the beginning of the distrib04.rc (initialize res11c) step. When the
> initialize fails, the restore fails, and the subsequent IPL of 132 will
> also
> fail.
>
> Please take a look at console log in my reproduction of the issue to
> confirm
> you are experiencing what I have describet.
>
> 10:54:02 HHCTA101I 0280: AWS Tape tape/k360n-ma108a.aws closed
> 10:54:02 HHCCP048I 0280:CCW=0F001C61 00000001=>F0F0F0F0 F0F2F4F4 F2F500C6
> 00090000 0000024425.F....
> 10:54:02 HHCCP075I 0280:Stat=2600 Count=0001
> 10:54:02 HHCCP076I 0280:Sense=40220000 00C00300 00000000 00800100 010000FF
> FF000000
> 10:54:02 HHCCP077I 0280:Sense=INTREQ EOC WRI
> 10:54:02 0280
> 10:54:02 260F
> 10:54:02 4002A
> 10:54:02 HHC1C001A Enter input for console device 001F
>
> 4002A is the code for the completion of the restore that is in distrib.rc.
> Notice message HHC1C001A: the restore application has issued a read to the
> console. Now start distrib04.rc.
>
> 10:54:15 script rc/distrib04.rc
> 10:54:15 # DISTRIB04 Initialize 2311 RES11C on 132
> 10:54:15 stopall
> 10:54:15 devinit 281 tape/k360n-ma110a.aws ro
> 10:54:15 HHCTA004I 0281: tape/k360n-ma110a.aws is a AWS Format tape file
> 10:54:15 HHCTA066I 0281: option 'ro' accepted.
> 10:54:15 HHCPN098I Device 0:0281 initialized
> 10:54:15 iplc 281
> 10:54:15 devinit 00c jcl/distrib04.jcl
> 10:54:15 HHCPN098I Device 0:000C initialized
> 10:54:15 HHCPN013I EOF reached on SCRIPT file. Processing complete.
> 10:54:15 HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6
> 10:54:15 PSW=00000005 C0000020 INST=D2FF11570156 MVC 343(256,1),342(0)
> move_character
> 10:54:15 R:001FFF57:K:06=00 00000000 00000000 00000000 000000
> ................
> 10:54:15 R:00000156:K:06=0000 00000000 00000000 00000000 0000
> ................
> 10:54:15 GR00=00000000 GR01=001FFE00 GR02=00000000 GR03=00000000
> 10:54:15 GR04=00000000 GR05=00000000 GR06=00000000 GR07=00000000
> 10:54:15 GR08=00000000 GR09=00000000 GR10=00000000 GR11=00000000
> 10:54:15 GR12=00000000 GR13=00000000 GR14=00000000 GR15=00000000
>
> The above addressing exception is normal and expected; the initialize
> program is determining the amount of memory installed. GR01 is very close
> to the 2MB line. The next message is much more interesting. It is a
> command reject by the console at X'01F'.
>
> 10:54:15 HHCCP048I 001F:CCW=020017E8 20000050=>00000000 00000000 00000000
> 00000000 ................
> 10:54:15 HHCCP075I 001F:Stat=0E00 Count=0050 =>00000000 00000000 00000000
> 00000000 ................
> 10:54:15 HHCCP076I 001F:Sense=80000000 00000000 00000000 00000000 00000000
> 00000000
> 10:54:15 HHCCP077I 001F:Sense=CMDREJ
>
> At this point, the initialize program has gone comatose. Initialize fails,
> and so the restore fails, and then the IPL 132 fails.
>
> There seem to be two workarounds.
>
> 1) When you get the command reject message, repeat at that point the step
> that you were attempting. I expect you will need to repeat 04 and 06.
>
> 2) When distrib03 (and 05) completes, type \ and enter before starting the
> next script to clear the outstanding read.
>
> Let me know how you make out. I will do some other tests and revise the
> web
> site based on your feedback and the additional testing.
>
> Best Regards,
> Steve Orso
>
>




[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Hi Michael:

Mark is spot-on with his description of the need to both respond "22" and hit the virtual Interrupt key by issuing a Hercules Ext command.


I concur with somitcw's suggestion regarding use of the Hercules Integrated Console: that is likely much easier than finding a Telnet that works well with Hercules 3.x.


And you are also right to thing that you can just re-initialize the one volume and retry. Nicely done.


A copy-paste of the relevant section of the Hercules console (if using the Integrated console) can be posted here, and if you are using the Hercules Integrated Console, we will be able to see both the DOS/360 and Hercules messages in the same list.


Good luck! And keep us posted on your progress.


Best Regards,
Steve Orso

[[e-mail] [hercules-390]]

I tried including the screenshot but can’t figure out how to do it.

Sent from my Windows 10 phone

From: ***@yahoo.com [hercules-390]
Sent: Monday, November 21, 2016 4:24 AM
To: hercules-***@yahoogroups.com
Subject: [hercules-390] Re: Can't IPL During Install of Hercules 3.07

 
Hi Michael:

OK, then it would appear that you are on step MIGRATE01, the first IPL of the restored distribution system, and that you have restored all tapes.  But based on what you say about Jason and tn3270, you have not seen much to let you know if the restores worked.  

I am not familiar with the Jason GUI...do you have a link?

DOS/360 did not have any support for 3270 devices as an operator console, so tn3270 will not help much either.  

And Hercules 3.07 did not support a wide range of telnet clients.  In particular, PuTTY will not connect.  I used a Windows NT Telnet client, which will not work so well on a Linux system if that's what you are using.  

I suggest you repeat the process using the Hercules integrated console.  The statements to do this are commented in the CNF files.  Just uncomment them, comment the original console statements, and prefix reponses to the restore program with a \ (backwards slash).  

That should give you console output to let you (and us) see how the restores are doing.  And if they fail, we can see logs that will help diagnose this.  

I agree with Mike that DOS/VS release 34 is more polished--it was in real life too--but I had a great time messing around with DOS/360--again, in real life too.  In the age of iPhones and GUI's, it's interesting to see what things were like 50 years ago.  

Best Regards,
Steve Orso


---In hercules-***@yahoogroups.com, <***@...> wrote :
Hi, Steve.  Thanks for following up - much appreciated!

Yes, I'm following your instructions. And, yes, I was trying to IPL from the 2311 on 132.

I think the first thing to fall back to is to delete everything and start over from the beginning.  I'll report back on how it goes.

Couple questions.  First, I was using the Jason GUI - could that have anything to do  with things?  Second, I have attempted to see the console output both using  Jason as well as using tn3270.  No dice.  How would you recommend connecting to see console output?

Again, many  thanks.

Michael




[Non-text portions of this message have been removed]