Re: Question: VS FORTRAN DCSS
This is what I have found on MAINT 319 minidisk (notes to users), file I5668806 MEMO: [qte] * Installation Section * FORMAT OF THE INSTALLATION TAPE: File 1: I5668806 026012 (Product Identifier file) I5668806 EXEC (Product Installation EXEC) File 2: I5668806 MEMO (Memo to Users) File 3: FORTRAN DEFAULTS (Required default files) [unqte] This file is missing from VSFORT 260 minidisk. Anyone having VS FORTRAN 2 (if any), please kindly have a look if this fi le is available, I am still inclined towards doing it proper way rather than restore SPTAPE with unknown version NSS/DCSS files. Alexey On Tue, 9 May 2006 01:37:35 -0400, Wayne T Smith [EMAIL PROTECTED] wrot e: When you generate the FORTVS2 MODULE, you are asked (or you specify via parameter, I forget) that you want one big MODULE, or a smaller MODULE and DCSS. We always used to generate and rename each, and had a stub module that would figure out which one to call at run-time. Sorry, I don't recall the DEFAULTS file. cheers, wayne =
Re: Question: VS FORTRAN DCSS
Just to notify - SPTAPE LOAD worked and I have restored the 'DSSVFORT DCS S' file to NSS spool area, after that VS Fortran 2 seems to work OK, at leas t I managed to run the verification procedure as per SC26-4339 document, which Larry Davis kindly provided link to. Thank you very much for your support, everyone, that really woke up some sort of nostalgy feelings abo ut computers I used to work at university (any PDP11-s left in this world?). I will proceed further to see if there are any other issues down there (aft er making DCSSBKUP, of course), as I have been asked already for a part-time administration of this system. Alexey On Tue, 9 May 2006 00:45:33 -0500, Alexey Bozrikov [EMAIL PROTECTED] wrote : [SKIPPED] What I found is an image of a tape (in so-called 'AWS' format), which seems to be SPTAPE-produced for the starter system. I MOVEFILEd some files from it and they seem to be NSS/DCSS files. Hopefully, if nothing has been changed since then I will be able to do an SPTAPE LOAD. I will investigate/report if any success will be achieved. Otherwise VS FORTRAN installation seem to have one file missing (all install EXECs ar e referring to FORTRAN DEFAULTS file, which is being read by EXECIO). Alexey [SKIPPED]
Re: VMRPC placement in z/VM 5.2
Hello Mats, The Programmer's Reference citation is correct. The VMRPC TXTLIB part is built on the TCPMAINT 492 test-build disk, and should then also reside on the client-code disk (TCPMAINT 592) when TCP2PROD is used to place files into production. The various client 'run-time' files are copied from the 492 disk to the 592 disk when a 'wildcard' CATALOG file entry (similar to the one that follows) is processed by TCP2PROD: BLD3Z BLD2Z * * = = The CATALOG file entries you cited are in place to specifically propagate the VMRPC TXTLIB to the MAINT 493 /193 disks, to ensure it is available f or use whenever the (CMS) DMSVSMAS module is built (without requiring a separate access of the TCPMAINT 592 disk beforehand). Regards, Mark Cibula, z/VM TCP/IP Development and Support
GCC compiler for CMS now available
Folks, for those of you that would like to try the GCC compiler (Version 3.2.3) in a CMS environment, an initial release is now available. The GCC compiler runs on any XA or ESA compliant version of VM and requires a small run time library. The compiler produces standard ASSEMBLER code that is assembled by the High Level Assembler. This means that C programs which use only the ANSI C library can be compiled and run on any version of ESA and z/VM. The compiler uses only traditional CMS and CMS emulated MVS system calls and so is an almost native GCC. Instructions on how to download and install it can be found here: http://www.vsoft-software.com/gccesa/ Suggestions for enhancements and improvements, especially in the run time support, are welcome. Enjoy! DJ
