开云体育

On Thu, Sep 3, 2020 at 11:15 AM, Jay Moseley wrote: > > On 9/3/20 9:36 AM, Bill Lewis wrote: > >> Is there JCL somewhere in that ISO to build the FORTRAN compiler? >> >> Bill > > Bill, > > Not in the

Bill, Not in the ISO, no, but you can look at this page to see the progress I made on the FORTRAN G and FORTRAN H compilers: http://www.jaymoseley.com/hercules/compilers/mvtsource.htm Beneath the

Is there JCL somewhere in that ISO to build the FORTRAN compiler? Bill

Hi folks, I am happy to release RPF 1.8.4. This release is merely a maintenance release. The code is heavily optimized. More than 1,300 lines are saved. And this release have modifications for the

I was able to use all of them from the object libraries in the DLIB set, but only was able to get the COBOL compilers (both E and F) to assemble and work in a z/OS 2.2 system.? Interestingly, the LE

The damaged IEYUNF has been replaced on the version of the OS/360 CD-ROM image available from my site: http://www.jaymoseley.com/hercules/downloads/archives/os360mvt.tar.gz Phil Roberts and I worked

I may have seen the sources you are looking for on Jay Moseley's syscpk;? They are around; if not on the image you have.? Some of the macro libs we have on the old systems are gems that don't even

Anyone had any success in getting any of these compilers to work? I am trying Fortran G (FO520). The source for IEYUNF is cut short, and there is no MACRO library so the provided source won't

Perhaps if Jay see's this.. Jay's current instructions have the DD in jes2 as //IDF0PDSI DD DSN=&N1..PROCLIB,DISP=SHR <---1ST CONVERTER etc. Jurgen, previous instructions and the usermod comments have

Right! Since an STC runs from the JES2 PROCLIB, shouldnt you have a JOBPROC card in the STC proc? :) The message you are getting is an "I" (information) level message, so no harm is being done. But if

Joe, My reading is that this would be in the JCL for the submitted job - on the //JOBPROC DD card. I haven't got as far as logging to TSO, or submitting a batch job. These messages appear just after

I see. Where is your SYSPROC=YES? Joe [email protected]> wrote:

Joe, Yes, I changed sys1.proclib(jes2) to include //IDF0PDSI DD DSN=&N1..PROCLIB,DISP=SHR <---1ST CONVERTER // DD UNIT=&U,VOL=SER=SYSCPK,DISP=SHR,DSN=SYSC.PROCLIB // DD DSN=&N2..PROCLIB,DISP=SHR // DD

Any idea what started task was STC 109?

[image: image.png] So, did you modify your JCL? If not, then the "I" message is simply telling you that. Joe [email protected]> wrote:

I have just built mvs38j, in accordance with Jay Moseleys latest instructions. I then installed Usermod #DYP001 - #DYP005, #DYPDMY, using Jay's dynproc.jcl. When I IPL the system, I get messages on

APPC and ASCH don't really have anything to do with the basic operation of VTAM terminals, also merely concatenating your datasets won't do anything except make the data available, you have to make

I did all the above and the system comes up much cleaner; but hercules tells me no 3270 device.I have to find out what devices are defined to MVS.? I had an assembler program the went through UCBs

Brian: yes,? I suspect that is the problem although I concatenated sys1.vtamlib and sys1.vtamlst from my old system which was working; but I still don't have a 3270 connection.? Fixing the problem

You have to have 3270's defined at the addresses that you have specified in your SYS1.VTAMLST(localconnectionsname), where localconnectionname is whatever you called your local terminals entry.? That