开云体育

Dagfinn, What is the purpose of the GO.SORTDD statement? You are allocating a new data set – but did NOT specify a volume serial Also, you should NOT need a COB.SYSLIB – this would be input to the

Frank You can look at SYS1.SYSGEN.SOURCE(IOGEN) On MY TK5 here is what I see //* DASD devices //* //* ! Devt ! Cua - Cua ! Cua - Cua ! Cua - Cua ! Cua - Cua ! Cua - Cua ! //*

The issue is the OLDER Sort Merge – did not support the newer DASD and Dynamic allocation When the TK5 was built – the newer product was installed and will now no longer require 2311 and 2314 And

Yes, the DASD are listed in the Hercules config file as well as (since I am running under VM) the VM directory for the MVS virtual machine. No problems there as the ICKDSF worked; I can also see them

Is this a general problem with TK5 that makes it difficult to use cobol/sort/merge or have Rob Prince made a different solution with the new DASD's in TK5. It seems you have followed the steps to add

I decided to go through the exercise of trying to add these volumes to my TK5 installation. I was able to successfully add the VTOC to the six volumes using ICKDSF, and was able to vary the volumes

Hi again I had to dig into this strange error message. So I went to our beloved cobol-74 manual and started reading about sort/merge statements. I read the example program in the manual and after a

Hi I am running this on my TK4 instance. The sort01-06 are in the dasd directory. So I am a bit confused and suspect there are some parameters missing i jcl/parm. ------------------------------

Did you create the 2314 DASD volumes you are asking it to use? SORT01, SORT02, etc. do not exist in the TK5 distribution as shipped.

If i run this without the GO,SORTDD statement i get the following error: +IER036I - B = 90 +IER037I - G = 2488 +IER038I - NMAX = 88920 +IER046A - SORT CAPACITY EXCEEDED +IER066A - APROX RCD CNT

Again - thank you for helping to solve this task. I have made some progress but receive a message about offline units needed. My jcl for cobol/sort and messages from sysout-console: /* //COB.SYSLIB DD

//GO.SORTWK01 DD UNIT=2314,SPACE=(TRK,(200,1)),VOL=SER=SORT01 //GO.SORTWK02 DD UNIT=2314,SPACE=(TRK,(200,1)),VOL=SER=SORT02 //GO.SORTWK03 DD UNIT=2314,SPACE=(TRK,(200,1)),VOL=SER=SORT03 //GO.SORTWK04

Hi, Mike, In the case of VM/370, you could use VMCF to communicate between virtual machines. For MVS, look here: /g/INTERCOMM Page down below the nice data center picture to read

DagFinn: Not quite – You do NOT need to pre-allocate any data sets in your step 3 Totally simply occupies space – that will never be used. In your STEP6 You will need to properly override the proc

That indeed worked like a charm. Thank you! kind regards Michael -- TK4- on virtual x86 Ubuntu LTS 22.04 VM/370 on virtual x86 Ubuntu LTS 22.04 Die Katze l?sst das Mausen nicht, Die Jungfern bleiben

Thanks for all info. I have adjusted the source/jcl but still get the same message. I provide the jcl with the pre-allocated files on sort volumes. Happy for all info that can solve this. //STEP03

Hi Dagfinn, From the format of the message IER040A I can see that you are using the original OS/360 Sort/Merge program in your MVS system. The reference manual for this program is GC28-6543 OS 360

Sort from the MVT Cobol compiler only works on 2311/2314 disks. Joe wrote:

Try to enter the JES2 command $p s1-9999 at the MVS console. It should purge some of these SYSLOG, if not immediately, then at the next IPL. Cheers, Rene FERLAND, Montreal

Dear Forum, I understand that programs/address spaces can exchange data/communicate with each other using common storage. What would be the best document to learn about how to do that? kind regards