开云体育

Your English isn't half bad, for a Brit. ;) [Dave runs for cover] -Dave -- Dave McGuire, AK4HZ New Kensington, PA

I wouldn’t know. I was never taught any English grammar. I was always encouraged to be expressive and not to worry about grammar or spelling. This was a problem when I came to write Fortran II

I might lose (a verb) ... but I very seriously doubt I would loose (an adjective). Joe

You would loose.. Dave Sent: 26 January 2021 13:02 To: [email protected] Subject: Re: [h390-vm] Two New Projects Tom, I'd be willing to bet that if you look at the PROFILE EXEC for gcccms and the

Tom, You should probably create a separate account for doing “C” development but that’s not trivial…. .. we still have two library problems… By default GCC targets PDPCLIB but it looks like

Also, I forgot to mention ... There are two flavors of C libraries on CMS. One is GCCLIB and the other is PDPLIB. I recommend you stick with GCCLIB and see what happens... Joe

Tom, I'd be willing to bet that if you look at the PROFILE EXEC for gcccms and the PROFILE EXEC for cmsuser you will find the problem. Youre probably missing a minidisk definition. Joe

Mr. Wade, When I started the porting effort, I had little or no knowledge of VM370. I have always been an application person. So I looking at logons, gcccms looked like the place for any "C"

The “h” files I am referring to are those for the “C” libraries. There are two sets and almost all “C” code needs at least one. I think you need to complain to the owner of the package.

Dave, The README file to which I am referring is on the github site (?github.com/tchandler48/cmsbasic ).? When one downloads the entire project, selecting the "Download Zip" option, the README file

Jim, Sorry for delay, been traveling. It looks like it did not link correctly. Based on comments on the list, I will load it under cmsuser and see what happens. Will get back to you. Tom C

Jim, Which README file? The problem is that there are two run-time libraries. One that is supplied with GCCCMS and which uses the OS macros, and one that has been written by VMers that uses the native

Hi Peter, Thanks for the feedback.? The instructions in the README file says to use GCCCMS although it also says it was tested in 6PExt. Does it not work in plain old 1.2 Sixpack?? Perhaps that's

Diagnose 58 is in the base VM/370. The base version only supports the X'19' CCW which is not a fullscreen interface. CLRSCRN, and my example program use Diagnose 5 with a X'19' CCW. That works fine on

If you look at the source for CLRSCRN it does not use DIAG 58 and works on systems without the DIAG 58 updates…. Dave Sent: 24 January 2021 14:09 To: [email protected] Subject: Re: [h390-vm] GCC

Here is a sample sequence: CLR CSECT USING NUCON,0 STM R14,R12,12(R13) LR R12,R15 USING CLR,R12 WAITT , WAIT FOR TERMINAL ACTIVITY TO STOP. L R3,ADEVTAB GET ADDRESS OF DEVICE TBL IN NUCON LH R2,0(R3)

My bad. DIAG 58 does full screen IO but if all you want to do is clear the screen there are simple IO sequences that do that without flipping to 3270 mode. Dave Sent: 24 January 2021 13:24 To:

Dave, I thought we were talking about a diag 58 call? Doesnt diag 58 do 3270 full screen IO? Joe

Hi Jim, I think your problems with NOT ATTACHED and NOT ACCESSED are arising because you are logged on to GCCCMS. I'd suggest trying to build the code while logged on to CMSUSER. GCCCMS is only for