+IER040A - INSUFFICIENT WORK UNITS
+IKF888I UNSUCCESSFUL SORT FOR WORK

Add sort work dd statements.

On Tue, Feb 27, 2024 at 10:30?AM Dagfinn Hammar <dagfinndh33@...> wrote:

Hi
Is there a solution for this error. Is there a jcl setup for cobol sort compile jobs?
HERC0101 STEP04 IEFBR14 RC= 0000
HERC0101 STEP05 IEBGENER RC= 0000
HERC0101 STEP06 COB IKFCBL00 RC= 0000
+IER040A - INSUFFICIENT WORK UNITS
+IKF888I UNSUCCESSFUL SORT FOR WORK
HERC0101 STEP06 GO LOADER RC= 0000
----------------------------------------------------
Dagfinn D. Hammar

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

Hi Robert,

I always used stopall instead of quiesce, because i heard that after quiesce restart is not possible.
But if you enter quiesce, then of course stopall is meaningless after that.
Is there any real advantages though?

Best wishes,
Andre

On 2024-02-26 18:52, Andre via groups.io wrote:

I must admit, i have OCD-like paranoia when it comes to system power down procedure.
Here is what i usually do:
1. Wait till my running jobs are finished.
2. Logoff all TSO sessions.
3. S SHUTDOWN
4.? Answer YES to following question:
??? *04 BPXI078D STOP OF ZFS REQUESTED. REPLY 'Y' TO? PROCEED. ANY OTHER REPLY WILL CANCEL THIS STOP.
5. $phasp (JES2 ENDED)
6. Z EOD ? (HALT EOD SUCCESSFUL)

6a: quiesce

7. stopall in Hercules console

Why would that be required?

Anyway, I finish with a script file containing "sfc xxx" for all my used-defined 3390's, after having run a job on z/OS to wipe the unused space (EOFDISK)

8. quit in Hercules console.

9. Make backups of your shadow disks, I keep 5 generations and run this bat file:

ren shadow-5 shadow-0
ren shadow-4 shadow-5
ren shadow-3 shadow-4
ren shadow-2 shadow-3
ren shadow-1 shadow-2
ren shadow-0 shadow-1
copy shadow\*.* shadow-1

Robert
--
Robert AH Prins
robert.ah.prins(a)gmail.com
The hitchhiking grandfather -
Some REXX code for use on z/OS -

Hello Patrik!

I must admit, i have OCD-like paranoia when it comes to system power down procedure.
Here is what i usually do:
1. Wait till my running jobs are finished.
2. Logoff all TSO sessions.
3. S SHUTDOWN
4.? Answer YES to following question:
??? *04 BPXI078D STOP OF ZFS REQUESTED. REPLY 'Y' TO? PROCEED. ANY OTHER REPLY WILL CANCEL THIS STOP.???????
5. $phasp (JES2 ENDED)
6. Z EOD ? (HALT EOD SUCCESSFUL)
7. stopall in Hercules console
8. quit in Hercules console. ???

Best wishes,
Andre

Patrik Schindler wrote:

]...]

Just for the record, for years I'm ending OS/390 by just
issuing a quit to the Hercules console to make it close
the disk files properly.

So you DO care about Hercules closing its disks properly but DON'T care about your OS/390 guest closing its disks properly?

You're a strange person, Patrik. :)

Of course I do this while the system is idle from user-
submitted jobs.

But to hell with any system processes who's disk buffers might not have been flushed yet? You don't care about those? They're not important, right?

Too lazy to manually wade through the shutdown sequence,
or trying to automate it as did TK4-.

Of course! No one wants to mess with any stinking automation after all. Just pull the plug!

Had not noticed any adverse effects.

Well, each guest is different I guess. OS/390 must obviously behave quite a bit differently than other guest operating systems.

Your mileage may vary.

Indeed. If it works for you? Fine.

But I personally would *never* publicly recommend such an irresponsible highly risky procedure to others.

But then as I guess you say, your mileage may vary. Right? >;-)

p.s. I'm curious: do you power off you Linux host operating system the same way? Just pull the plug?

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...

Patrik,

Are you still talking Z/OS, or OS/390?

For Z/OS, you might want to investigate "S SHUTDOWN"

Chris
--
<cjar1950@...>



----------------------------------------------------------------------------------------------------------------------------------
On Mon, 26 Feb 2024 09:54:12 +0100
"Patrik Schindler" <poc@...> wrote:

Hello Andre,

Am 25.02.2024 um 22:07 schrieb Andre via groups.io <procritic@...>:

I don't want to hurt my system with emergency shutdown, is there any way to reconnect to MVS console using 3270?

Just for the record, for years I'm ending OS/390 by just issuing a quit to the Hercules console to make it close the disk files properly. Of course I do this while the system is idle from user-submitted jobs. Too lazy to manually wade through the shutdown sequence, or trying to automate it as did TK4-. Had not noticed any adverse effects. Your mileage may vary.

:wq! PoC

Hello Andre,

Am 25.02.2024 um 22:07 schrieb Andre via groups.io <procritic@...>:

I don't want to hurt my system with emergency shutdown, is there any way to reconnect to MVS console using 3270?

Just for the record, for years I'm ending OS/390 by just issuing a quit to the Hercules console to make it close the disk files properly. Of course I do this while the system is idle from user-submitted jobs. Too lazy to manually wade through the shutdown sequence, or trying to automate it as did TK4-. Had not noticed any adverse effects. Your mileage may vary.

:wq! PoC

开云体育

Yay!! It worked! Thank you so much Piotr! I am saved!

Best wishes,
Andre

Hello Piotr!

vary is a MVS console command, which i dont have

Andre

Hello Everyone!

Please help! I am so stupid, started IPL of z/OS with no 3270s opened.
So i don't have MVS console window now. Only TSO.
In my config there was no 3215-C either, so / commands from Hercules console doesn't work.
I don't want to hurt my system with emergency shutdown, is there any way to reconnect to MVS console using 3270?

Andre :(

Hi,

I have added TK5.SHELBY.EZASMI.V100.ZIP in the MVS-TK5 system.
This will be available in MVS-TK5 Update-03, which will be released
in April or May.

Cheers,
Rob