开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. H390-MVS
  2. Messages
Expanded Topics Messages Polls
Date
Re: PL/I SELECT statement Supported?

 

On 28/02/2025 03:39, bufbooth via groups.io wrote:
Hello All, does the version of PL/I that Hercules/MVS38 use support the SELECT/WHEN statement?? I get a compile errors on any SELECT statement.? Thank you, Dennis
If you go to my website at :

applewood.linkpc.net/files/MVS380/pdfs?? then go to folder PL1


you will find all the manuals related to PL1 and programming etc under MVS.
Re: PL/I SELECT statement Supported?

 

I mean in the file section of the Pl1f-And-Mvs38j group.
?
Marco
  • ?
?
Re: PL/I SELECT statement Supported?

 

Do you have an example of the macro that is needed?
Thanks...
Re: PL/I SELECT statement Supported?

 

No, but there are macros in the file section with the statement you need.
?
Marco
Re: Work with your Turnkey System like you are scientist from NASA!

 

开云体育

Thanks for the info … these will be very interesting to browse through!

Jim

On Feb 25, 2025, at 3:03?PM, Andre via groups.io <procritic@...> wrote:

?
Hello guys,
?
Just wanted to share with you this publicly available NASA documents:
?
Mission and data operations IBM 360: User's guide (1971)
?
Mission and data operations IBM 360 user's guide (1973)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 1: System overview (1978)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 2: User's reference manual (1978)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing System (EOD-LARSYS)
user guide for the IBM 370/148. Volume 3: As-built documentation (sections 1-12) 1980
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing System (EOD-LARSYS)
user guide for the IBM 370/148. Volume 3: As-built documentation (sections 13-23) 1980
?
Earth Observations Division verison of the Laboratory for Applications of remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 4: Program listings
?
If you like stuff like that, please search for "IBM" on this site and you will find dozens of programs for IBM 360/370 that NASA used in 60s-70s.
?
Best wishes,
Andre
?
?
Re: zOS shutdown in Hyperion

 

It seemss You have Netview active on z/OS, if the STC name is CNMPROC, try this NCCF cmd:

F CNMPROC,NCCF EXCMD AUTO1 SHUTSYS

Hope this help
Bye
PL/I SELECT statement Supported?

 

Hello All, does the version of PL/I that Hercules/MVS38 use support the SELECT/WHEN statement?? I get a compile errors on any SELECT statement.? Thank you, Dennis
Re: DLI loading on Tk4 and MVSCE?

 

On 2/26/25 13:22, John James via groups.io wrote:
P.S. Is there is user guide available anywhere for RECV370? Darned if I can remember how to use it. Thanks.
The source is included on SYSCPK, and also available at CBT:

Re: How to link mainprogram and subprogram in MVT Cobol

 

Thank you. Ok. I see in which direction it goes. In GC28-6399 COBOL_Compiler_and_Library Manual, SYSIN is not mentioned. But I found it in GC26-4061-1_MVS_370_Linkage_Editor_Users_Guide_Dec85. With this concatenation I could ad statements to the load editor:
?
//SYSLIN DD DSN=&TEMP,DISP=SHR
//? ? ? ? ? ? ? ?DD DDNAME=SYSIN
//SYSIN DD *
? INCLUDE .....
? NAME ....
/*
?
And if I may say so. I am absolutely thrilled when I see who has replied to me. I've been a fanatical MVS/Hercules fan for 3 years and you guys are my heroes!!! And then of course there's Moshix!
?
Thank you,
Simon
?
Re: zOS shutdown in Hyperion

 

On Wed, Feb 26, 2025 at 07:23:23PM +0000, Erics51 via groups.io wrote:

All the docs I’ve found give the same instruction on how to cleanly shutdown the zOS session, namely
# in "system" terminal:
S SHUTSYS
Z EOD

# then, once finished, in Hercules:
exit
So I assume it should exist.
I would only assume it would exist if running the exact z/OS system the doc
was written for. Startup/shutdown procedures could vary greatly from one
shop to another, especially if automation products were in use. My previous
employer used AF/Operator to automate things. It intercepted some console
commands, like the start and stop commands, and for tasks it was configured
to control it would take the steps necessary to get the task into the
desired state. For example, a P CICS command might issue a F CICSP1,CEBT P
SHUTDOWN command behind the scenes. If anyone is interested in seeing a real
world example from a former z/OS shop, my former employer's shutdown
procedure looked something like (commands are in all upper case, comments
are in mixed case):


-------- Initiators ----------------------------------------
Drain the initiators:
INITOFF

-------- Printers ------------------------------------------
Stop the printers:
$P PRT1
$P PRT4
$P PRT5
$P PRT7

-------- Batch Jobs ----------------------------------------
Cancel Jobs:
Terminate any active batch jobs so CA7 and DISPATCH will
have correct status.

-------- CICS and IMS --------------------------------------
Stop GROUP4 tasks

Use command 'D GROUP4' to display desired and actual status.

Stop all CICS regions by issuing commands:
P CICS
P CICSA
P CICSB
P CICSC
P CICSD

Wait for the CICS regions to terminate.
Status can be checked by issuing the 'D GROUP4' command.

After the CICS regions have terminated, stop the IMS regions with commands:
P IMSPDBC
P IMSTDBC
P IMSXDBC

Wait for the IMS regions to terminate.

Wait for GROUP4 tasks to complete termination.
Use command 'D GROUP4' to display desired and actual status.

Note any tasks which have to be cancelled.

-------- Post-VTAM Tasks -----------------------------------
After the GROUP4 tasks have completed termination, stop the GROUP3 tasks.
P GROUP3

Wait for GROUP3 tasks to complete termination.
Use command 'D GROUP3' to display desired and actual status.

Note any tasks which have to be cancelled.

-------- DISPATCH and CA7 ----------------------------------
After the GROUP3 tasks have completed termination, stop the GROUP2 tasks.

Ensure ALL batch jobs are complete so CA7 will have complete status.
Cancel any remaining batch jobs.

P GROUP2

Wait for GROUP2 tasks to complete termination.
Use command 'D GROUP2' to display desired and actual status.

Note any tasks whcih have to be cancelled.

-------- VTAM and Pre-VTAM Tasks----------------------------
After the GROUP2 tasks have completed termination, stop the GROUP1 tasks.
P GROUP1

Wait for GROUP1 tasks to complete termination.
Use command 'D GROUP1' to display desired and actual status.

Note any tasks which have to be cancelled.

After all GROUP1 tasks have stopped, display AFOPER status.
D GROUP*

-------- AFOPER --------------------------------------------
Stop AFOPER
P AFOPER

Wait for AFOPER to complete termination.

-------- OMVS ----------------------------------------------
Shutdown all OMVS and HFS activity.
F OMVS,STOPPFS=NFS Stop NFSC
R nn,Y
R nn,I

F OMVS,STOPPFS=ZFS Stop ZFS
R nn,Y
R nn,I

F OMVS,SHUTDOWN Stop OMVS

Wait for OMVS shutdown complete message.

-------- JES2 ----------------------------------------------
Stop JES2
$PJES2,TERM

-------- SMF -----------------------------------------------
Flush SMF buffers:
Z EOD

-------- SYSPLEX -------------------------------------------
Enter the following commands from a CFL2 MCS console:

V XCF,CFL1,OFFLINE

Wait for:
xx IXC371D CONFIRM REQUEST TO VARY SYSTEM CFL1 OFFLINE.

R xx,SYSNAME=CFL1

Wait for this message:

xx IXC102A XCF IS WAITING FOR SYSTEM CFL1 DEACTIVATION. REPLY DOWN WHEN
MVS ON CFL1 HAS BEEN SYSTEM RESET

R xx,DOWN

------------------ End of Shutdown Procedure ------------------------

--

Kevin


Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
Re: zOS shutdown in Hyperion

 

just in case you are using an ADCD distro: In that case the magic command is "S SHUTDOWN" ?
Re: zOS shutdown in Hyperion

 

All the docs I’ve found give the same instruction on how to cleanly shutdown the zOS session, namely
# in "system" terminal:
S SHUTSYS
Z EOD

# then, once finished, in Hercules:
exit
So I assume it should exist.

Regards
Eric Silvester
On 26 Feb 2025 at 00:03 +0000, Vince Coen via groups.io <vbcoen@...>, wrote:

Quick guess is that you do NOT have a procedure installed called shutsys

May be need to look for the correct way - I seem to recall I had to run
a few procedures to close everything down before doing the final
quiesce? or something similar but may be spelt differently - it was a
few years ago :)

There is NOT a one process that does it all i,e similar to TK4 or 5 and
I would have to reread the manual/book for it - a RED BOOK being but one.




On 25/02/2025 20:48, Erics51 via groups.io wrote:
Running Hyperion dev branch 4.8 on Apple M2 hardware and can
successfully start z/OS (V2.2, 22.5 & 3.1) but can't shut them down
cleanly.? Issuing S SHUTSYS fails on every system - see below
?- 19.27.49 ? ? ? ? ? s shutsys
?- 19.27.49 ? ? ? ? ? IRR812I PROFILE * (G) IN THE STARTED CLASS WAS USED
?- ? ? ? ? TO START SHUTSYS WITH JOBNAME SHUTSYS.
? ?19.27.49 STC02511 ?IEFC452I SHUTSYS - JOB NOT RUN - JCL ERROR
? ?19.27.49 ? ? ? ? ? IEE122I START COMMAND JCL ERROR
I must be doing something wrong with. Any suggestions?
Re: DLI loading on Tk4 and MVSCE?

 

Allan, yes, that's a pretty good summary of why you'd probably have to be insane to try to get IMS/360 DL/I (especially what appears to be a beta version) working on MVS.
?
Which I suppose is where I come in. Looks like a nice little project to me, especially as there's no pressure or a given target date. I can take as much time as I like.
?
As far as the OSAM DCB is concerned, I imported an MVT copy of SYS.1.MACLIB into MVS, and used it for the IMSGEN, PSBGEN, and DBDGEN. Has worked fine so far.
?
The OSAM SVC was no problem. For convenience, I copied it into SYS1.LPALIB as SVC 233, an unused Type 4 slot on TK4-, and it's working fine. It's a very small piece of code that, as far vas I can see, should run as any SVC type.
?
The matter of the OSAM channel-end appendage and the IEAAPP00 SYS1.PARMLIB member was straightforward to address. I created the IEAAPP00 member with some help from the good folk on this forum.
?
At that point, DL/I loaded up a database with new main segments. But, as I had expected, in the next test the load of dependent segements into the OSAM file failed because the OSAM DEB had been GETMAINed from the wrong subpool (from subpool zero, when in MVS it should be subpool 230). The offending module is DFSIOS10, but the source code that we have is incomplete. So my next task is to use a disassembler (as supplied to me by the ever-helpful Jay Moseley) to make changes to that module. No doubt there will be more problems to solve after that. I think this little project is going to give me something interesting to do for some time yet.
?
Regards, JJ
?
P.S. Is there is user guide available anywhere for RECV370? Darned if I can remember how to use it. Thanks.

Re: zOS shutdown in Hyperion

 

Hi R别苍é?

Tried S SHUTALL but with the same outcome sadly.

Regards
Eric Silvesterr
Re: How to link mainprogram and subprogram in MVT Cobol

 

On 2/23/25 12:29, ssulser via groups.io wrote:
Hi
Can somebody please explain, whats the purpose of the DD DDNAME=SYSIN statement here? What does it reference to? SYSIN was used as source input dataset for the COBOL compiler and SYSLIN is the object module. I don't understand that. Thank you very much.
It allows you to append control statements to the SYSLIN dataset. You might include statements to supply additional directives to the Link Editor, such as NAME, ORDER, etc.
Re: Work with your Turnkey System like you are scientist from NASA!

 

开云体育

Thanks André, very nice!

搁别苍é.

On 25 Feb 2025, at 22:03, Andre via groups.io <procritic@...> wrote:

Hello guys,
?
Just wanted to share with you this publicly available NASA documents:
?
Mission and data operations IBM 360: User's guide (1971)
?
Mission and data operations IBM 360 user's guide (1973)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 1: System overview (1978)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 2: User's reference manual (1978)
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing System (EOD-LARSYS)
user guide for the IBM 370/148. Volume 3: As-built documentation (sections 1-12) 1980
?
Earth Observations Division version of the Laboratory for Applications of Remote Sensing System (EOD-LARSYS)
user guide for the IBM 370/148. Volume 3: As-built documentation (sections 13-23) 1980
?
Earth Observations Division verison of the Laboratory for Applications of remote Sensing system (EOD-LARSYS)
user guide for the IBM 370/148. Volume 4: Program listings
?
If you like stuff like that, please search for "IBM" on this site and you will find dozens of programs for IBM 360/370 that NASA used in 60s-70s.
?
Best wishes,
Andre
?
?
Re: zOS shutdown in Hyperion

 

I'm definitely doing something wrong.? I'm trying to run 2.5 and can only re-ipl by doing a quiesce first.
?
I can only see two terminals (0060,0061) and 0060 is used for the console.
Also, there's no printer defined and 00E/00F do not exist.? Do I need to gen additional hardware with HCD?
?
Can I pick your brain off list?
?
PS-I'm an MVS newbie!
Re: How to link mainprogram and subprogram in MVT Cobol

 

//LKED.SYSIN DD *
?Statements to include additional programs into load module.
/*

Include copies the member (subroutine) into the object module
Library sets up the member (subroutine) to be separately?loaded during runtime.

On Tue, Feb 25, 2025 at 5:19?PM ssulser via <ssulser=[email protected]> wrote:
Hi
?
Can somebody please explain, whats the purpose of the DD DDNAME=SYSIN statement here? What does it reference to? SYSIN was used as source input dataset for the COBOL compiler and SYSLIN is the object module. I don't understand that. Thank you very much.
?
?
COBUCL procedure:
?
//COBUCL ?PROC CPARM1='LOAD,SUPMAP', ? ? ? ? ? ? ? ? ? ? ? ?
// ? ? ? ? ? ? CPARM2='SIZE=2048K,BUF=1024K', ? ? ? ? ? ? ??
// ? ? ? ? ? ? LKEDPGM='IEWL' ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
//COB ?EXEC ?PGM=IKFCBL00,REGION=4096K, ? ? ? ? ? ? ? ? ? ??
// ? ? ? ? ? PARM='&CPARM1,&CPARM2' ? ? ? ? ? ? ? ? ? ? ? ??
//SYSPRINT ?DD SYSOUT=* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
//SYSUT1 DD UNIT=SYSDA,SPACE=(460,(700,100)) ? ? ? ? ? ? ? ?
//SYSUT2 DD UNIT=SYSDA,SPACE=(460,(700,100)) ? ? ? ? ? ? ? ?
//SYSUT3 DD UNIT=SYSDA,SPACE=(460,(700,100)) ? ? ? ? ? ? ? ?
//SYSUT4 DD UNIT=SYSDA,SPACE=(460,(700,100)) ? ? ? ? ? ? ? ?
//SYSLIN DD DSN=&LOADSET,DISP=(MOD,PASS),UNIT=SYSDA, ? ? ? ?
// ? ? ? ? ? ? SPACE=(80,(500,100)) ? ? ? ? ? ? ? ? ? ? ? ??
//LKED EXEC PGM=&LKEDPGM, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
// ? ? ? ? ?PARM='LIST,XREF,LET',COND=(5,LT,COB),REGION=96K?
//SYSLIN ?DD DSN=&LOADSET,DISP=(OLD,DELETE) ? ? ? ? ? ? ? ??
// ?DD ?DDNAME=SYSIN ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
//SYSLMOD DD DDNAME=SYSLMOD ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
//SYSLIB DD ? DSN=SYS1.COBLIB,DISP=SHR ? ? ? ? ? ? ? ? ? ? ?
//SYSUT1 DD UNIT=SYSDA,SPACE=(1024,(50,20)) ? ? ? ? ? ? ? ??
//SYSPRINT DD SYSOUT=* ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?



--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?
Re: How to link mainprogram and subprogram in MVT Cobol

 

On Tue, Feb 25, 2025 at 03:19 PM, <ssulser@...> wrote:
Can somebody please explain, whats the purpose of the DD DDNAME=SYSIN statement here? What does it reference to?
It is a concatenation statement for SYSLIN, typically to provide linker statements which, for example, would allow you to link/edit your main object module (the one defined by SYSLIN) with some other object module(s) from an other library, or to name the final object module produced by the linker.
?
If you don't need it, you can ignore it. This will generate a warning but the link/edit will proceed normally.
?
Cheers,
?
Rene FERLAND, Montreal
Re: zOS shutdown in Hyperion

 

Quick guess is that you do NOT have a procedure installed called shutsys

May be need to look for the correct way - I seem to recall I had to run a few procedures to close everything down before doing the final quiesce? or something similar but may be spelt differently - it was a few years ago :)

There is NOT a one process that does it all i,e similar to TK4 or 5 and I would have to reread the manual/book for it - a RED BOOK being but one.

On 25/02/2025 20:48, Erics51 via groups.io wrote:
Running Hyperion dev branch 4.8 on Apple M2 hardware and can successfully start z/OS (V2.2, 22.5 & 3.1) but can't shut them down cleanly.? Issuing S SHUTSYS fails on every system - see below
?- 19.27.49 ? ? ? ? ? s shutsys
?- 19.27.49 ? ? ? ? ? IRR812I PROFILE * (G) IN THE STARTED CLASS WAS USED
?- ? ? ? ? TO START SHUTSYS WITH JOBNAME SHUTSYS.
? ?19.27.49 STC02511 ?IEFC452I SHUTSYS - JOB NOT RUN - JCL ERROR
? ?19.27.49 ? ? ? ? ? IEE122I START COMMAND JCL ERROR
I must be doing something wrong with. Any suggestions?
41 - 60 of 5213