Hello,

I like reading printouts of listing and source code.? Is there a method (and what is it) to:

1) Connect a VM system to my Brother laser printer?

2) Rotate to landscape listing printouts?

3) Print source code in portrait mode?

4) On the source code is there a method to update the source code with update files?

Thank you.

Bertram,

I guess what you are asking needed a weeks training course followed by lots of practice on return. I remember a very frustrating week in the IBM training Center in ST. Johns Wood, London building CP and CMS in a second level machine on a very underpowered 43xx. Very slow.

?

Well many many reasons the updated source isn’t stored anywhere so to view current source you need to apply the updates.

=> don’t ask for this to change as my answer will be rude and offensive => just live with it.

?

For CP “VMSETUP CP” access the disks with the source. Then apply the updates e.g.

?

update dmkcfc assemble * dmkhrc (ctl???????????????????????????????????????????????????????????????????????????????????????????????

UPDATING 'DMKCFC ASSEMBLE I1'.?????????????????? ???????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R08928DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R09413DK H1'.?????????? ???????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R10076DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R10847DK H1'.?? ???????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R12101DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R12794DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R13360DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R13648DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R13704DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC R12658DK H1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC010DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC013DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC018DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????? ???????

APPLYING 'DMKCFC HRC019DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC021DK F1'.?????????????????????????????????????????????????????????????????????????????????????? ???????????????

APPLYING 'DMKCFC HRC026DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC030DK F1'.?????????????????????????????????????????????????????????????????????????????? ???????????????????????

APPLYING 'DMKCFC HRC043DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

APPLYING 'DMKCFC HRC107DK F1'.?????????????????????????????????????????????????????????????????????? ???????????????????????????????

APPLYING 'DMKCFC HRC068DK F1'.?????????????????????????????????????????????????????????????????????????????????????????????????????

Ready; T=0.06/0.15 08:23:43???????????????????????????

?

Which leaves us with a $DMKCFC ASSEMBLE on our “A” disk containing the modified source.

This also has comments with the module name in inserted/modified likes. So searching for “HRC010DK will show the lines modified.

How did I know DMKCFC was one of the modules patched for HCP, well HRCMODS MEMO F contains a list of modifications.

It tells me HCP is modification HRC010DK and the HRC010DK MEMO F has the details.

I could also just do “LIST * HRC010DK *” and it would show the change files for HCP.

As I knew HCP was all new code I didn’t bother updating the source I simply looked at the updates.

?

To save changes -? I’ll answer separately.

?

When you say “build without TEX what” are you asking.

All the original TEXT files are on the disks. You can build a base VM system by releasing the disks with the mods and rebuilding CMS and CP with the IBM control files.

Its not terribly useful to do this as most things simply won’t work.

?

As Joe says there is a lot of detail in MAINT MEMO. In fact memo files contain much of the docs so doing

?

VMSETUP CP (or CMS)

FSLIST * MEMO *

?

May help.

?

Dave

?

?

From: [email protected] <[email protected]> On Behalf Of Bertram Moshier
Sent: 06 December 2022 04:44
To: [email protected]
Subject: [h390-vm] What is the proper way to look at ...

?

Hello,

?

What is the command (or proper method) to look at the VM/CE source?? I mean the based code with the updates??

?

How do I save changes I make in base delta form? (Base new update?)

?

Is the a method for rebuilding VM/CE from scratch (without using the supplied TEX files)?

?

I apologize for missing this information.

?

Thank you.

On Sat, 2022-12-03 at 15:10 -0800, David Durand wrote:

From: Bertram Moshier

12:12pm???#4785??

Hi,

?

IMHO, it isn't Hercules responsibility to handle the DIAG8CMD OFF beyond a program check.

?

It is the responsibility of the OS issuing the DIAG to Hercules.? Why?? It is how it would work with real iron.

?

The OS should capture the check and reflect it back to the user who attempted to issue the Hercules command.

?

In the case of VM/CE the return would be an error message and return code stating Herclues has DIAG8CMD off.

?

Thank you

I'm not going to push this much farther, as it's just an idea, but your description does not necessarily match what the real machines would do, because the state of a machine after a diagnose command is issued is dependent on the exact model (and even the field revision state) of that machine. This would be true even if though there are some "standard" diagnose functions some later models.

It's an operating system's responsibility to know?before issuing a diagnose, that it will not cause a problem. The 1987 version of the 370-XA Prince of Ops, and earlier 370 versions indicates that the Model and Version fields of the data returned by STIDP would be used to make that determination:

DIAGNOSE, unlike other instructions, does not follow the rule that programming errors are distinguished from equipment errors. Improper use of DIAGNOSE may result in false machine-check indications or may cause actual?machine malfunctions to be ignored. It may also alter other aspects of system operation, including instruction execution and channel- program operation, to an extent that the operation does not comply with that specified in this publication. As a result of the improper use of DIAGNOSE, the system may be left in such a condition that the power-on reset or initial-microprogram-loading (IML) function must be performed. Since the function performed by DIAGNOSE may differ from model to model and between versions of a model, the program should avoid issuing DIAGNOSE unless the program recognizes both the model number and version code stored by STORE CPU 10.?

So handling the exception is Hercules-specific, and has nothing to do with a "real" 370. So whatever we do is an?

I took a look at the source, and it seems that the Hercules options defined in feat370.h includes FEATURE_HERCULES_DIAGCALLS. This means that it should generally be possible to check to check if DIAG 008 is enabled in the configuration by the use of other Hercules-specific diagnose calls. So it's certainly reasonable to argue that this crash can be handled in CP, and therefore should be.

There are no Hercules-specific diagnose calls that could be queried for this information. ? There are some Hercules-specific diagnose calls, but not a "query" mechanism, per se. ?

I agree that a patch to the HCP command to check that it's running under Hercules would be a good idea. I also think there's an argument that a Hercules console message for illegal DIAGNOSE instructions could be helpful in the presumably rare case where an OS performs a DIAGNOSE instruction incorrectly, and it does seem easy to implement.

From: Bertram Moshier

12:12pm???#4785??

Hi,

?

IMHO, it isn't Hercules responsibility to handle the DIAG8CMD OFF beyond a program check.

?

It is the responsibility of the OS issuing the DIAG to Hercules.? Why?? It is how it would work with real iron.

?

The OS should capture the check and reflect it back to the user who attempted to issue the Hercules command.

?

In the case of VM/CE the return would be an error message and return code stating Herclues has DIAG8CMD off.

?

Thank you

I'm not going to push this much farther, as it's just an idea, but your description does not necessarily match what the real machines would do, because the state of a machine after a diagnose command is issued is dependent on the exact model (and even the field revision state) of that machine. This would be true even if though there are some "standard" diagnose functions some later models.

It's an operating system's responsibility to know?before issuing a diagnose, that it will not cause a problem. The 1987 version of the 370-XA Prince of Ops, and earlier 370 versions indicates that the Model and Version fields of the data returned by STIDP would be used to make that determination:

DIAGNOSE, unlike other instructions, does not follow the rule that programming errors are distinguished from equipment errors. Improper use of DIAGNOSE may result in false machine-check indications or may cause actual?machine malfunctions to be ignored. It may also alter other aspects of system operation, including instruction execution and channel- program operation, to an extent that the operation does not comply with that specified in this publication. As a result of the improper use of DIAGNOSE, the system may be left in such a condition that the power-on reset or initial-microprogram-loading (IML) function must be performed. Since the function performed by DIAGNOSE may differ from model to model and between versions of a model, the program should avoid issuing DIAGNOSE unless the program recognizes both the model number and version code stored by STORE CPU 10.?

So handling the exception is Hercules-specific, and has nothing to do with a "real" 370. So whatever we do is an?

I took a look at the source, and it seems that the Hercules options defined in feat370.h includes FEATURE_HERCULES_DIAGCALLS. This means that it should generally be possible to check to check if DIAG 008 is enabled in the configuration by the use of other Hercules-specific diagnose calls. So it's certainly reasonable to argue that this crash can be handled in CP, and therefore should be.

I agree that a patch to the HCP command to check that it's running under Hercules would be a good idea. I also think there's an argument that a Hercules console message for illegal DIAGNOSE instructions could be helpful in the presumably rare case where an OS performs a DIAGNOSE instruction incorrectly, and it does seem easy to implement.