Re: Rexx Alternate library
Here's my VMARC. Be sure to look at my fixed version of EAGACTAL EXEC. The original version had 2 problems and bad RAS: - it ran with the default ADDRESS CMS, what is not good for RAS reasons, I changed it to ADDRESS COMMAND. I had to uppercase one letter in an option of one COPYFILE command. - it could display a nasty errormsg: DMSNXD616W EAGRTPRC does not exist. This alarms the end-user, but would not indicate a problem. This is fixed by running with ADDRESS COMMAND. - the verification procedure failed always: it tried to COPYFILE the compiled verification execs from the wrong place. 2007/8/13, Tracy Dean [EMAIL PROTECTED]: On Fri, 10 Aug 2007 16:04:34 +0300, Kris Buelens [EMAIL PROTECTED] wrote: ... Question: is someone from the VM lab listening and able to get a repaire d version of the alternate library on http://www-306.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.htm l ... We're looking into it (including providing the package in VMARC format.) Thanks, Tracy Dean, IBM -- Kris Buelens, IBM Belgium, VM customer support
Re: Rexx Alternate library
On Fri, 10 Aug 2007 16:04:34 +0300, Kris Buelens [EMAIL PROTECTED] wrote: ... Question: is someone from the VM lab listening and able to get a repaire d version of the alternate library on http://www-306.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.htm l ... We're looking into it (including providing the package in VMARC format.) Thanks, Tracy Dean, IBM
Re: Rexx Alternate library
I downloaded the ZIP file too, and it is definitely broken. The proposed FTP commands are surely wrong too all the time. I don't recognize the record packing as something standard (but I'm not specialized in all possible blocking methods). The records are prefixed by 3 bytes: a flag and a 2 byte lrecl. With a simple REXX exec, I was able to reconstruct valid files. Followed by some COPYFILEs to make some files RECFM F. This was however not enough. The EAGACTAL EXEC has a bug in its verification process: it tries to COPY the VALTLIB CEXEC/REXXMOD into EXEC/MODULE on the target disk, but it did leave tses files on the source disk I'll send Adam a VMARC with the corrected files. Question: is someone from the VM lab listening and able to get a repaired version of the alternate library on http://www-306.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.html -- Kris Buelens, IBM Belgium, VM customer support
Re: Rexx Alternate library
I'll repeat my conclusion: I downloaded the ZIP file too, and it is definitely broken. The proposed FTP commands are surely wrong too all the time. I don't recognize the record packing as something standard (but I'm not specialized in all possible blocking methods). The records are prefixed by 3 bytes: a flag and a 2 byte lrecl. With a simple REXX exec, I was able to reconstruct valid files. Followed by some COPYFILEs to make some files RECFM F. This was however not enough. The EAGACTAL EXEC has a bug in its verification process: it tries to COPY the VALTLIB CEXEC/REXXMOD into EXEC/MODULE on the target disk, but it did leave these files on the source disk The files must be uploaded in binary to VM, during upload RECFM and LRECL have no importance; the records must be reconstructed by interpreting the 3 bytes the record prefix; what I did with a simple exec. I'm just a ordinary field Systems Engeneer with some free time these days, so I could look into this. But, the official owner at IBM of these files should provide a good version. And as suggested it would better be in VMARC format as then that repository can be unpacked on VM, preserving RECFM/LRECL/timestamp of all its members. In the mean time, I can send my fixed version in a VMARC. 2007/8/10, Lionel B. Dyck [EMAIL PROTECTED]: From reading this thread I must have missed the solution - can someone summarize the solution to a correct upload/installation? Question: why doesn't IBM just include this with the base z/VM distribution? It is free and needed by several other IBM products so why not make it easier for your customers? TIA -- *Lionel B. Dyck, Consultant/Specialist * Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED][EMAIL PROTECTED] AIM: lbdyck *|* Yahoo IM: lbdyck * * -- Kris Buelens, IBM Belgium, VM customer support
Re: Rexx Alternate library
On Aug 10, 2007, at 8:04 AM, Kris Buelens wrote: I'll send Adam a VMARC with the corrected files. Which Kris did! My thanks. Of course, once I got it installed, I found out that IPGATE can't run with the alternate library, so I'm using the interpreted version *anyway*, but at least I have the alt lib installed and working now. Question: is someone from the VM lab listening and able to get a repaired version of the alternate library on http://www-306.ibm.com/ software/awdtools/rexx/rexxzseries/altlibrary.html Adam
Re: Rexx Alternate library
Question: why doesn't IBM just include this with the base z/VM distribution? It is free and needed by several other IBM products so why not make it easier for your customers? DEC used to ship all the runtime libraries for all supported languages because DEC engineering wrote at least one utility in every supported language. Was a neat trick to force the marketing dweebs to ship all the runtime libraries in the base OS package...
Re: Rexx Alternate library
From reading this thread I must have missed the solution - can someone summarize the solution to a correct upload/installation? Question: why doesn't IBM just include this with the base z/VM distribution? It is free and needed by several other IBM products so why not make it easier for your customers? TIA Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
Re: Rexx Alternate library
If you talking about VMS, they had a single common runtime, THEN built th e compilers. IBM had to do it the other way around, combining existing runtimes to form LE, and i t was a MESS!
Rexx Alternate library
So, I'm trying to get IPGATE to work on a new system. It has certain prereqs, among them MTREXX and the compiled Rexx runtime. MTREXX was no problem. However.the Rexx runtime is quite a challenge. Sure, you can download it. It arrives as a zip file. You unzip it on your desktop. There's an ftpput.cmd file which shows the commands you need (mode E, type B, lrecl, and so on). Problem is, it doesn't work. The EAGACTAL EXEC file that is produced is unreadable. Retransmitting it as F 80 does indeed produce something that looks like an EXEC, and that runs. Then it complains that it couldn't actuallywell: EAGACTAL: Install and activate the Alternate Library 1. Verify if a REXX Runtime Library exists already: A REXX Runtime System does not exist. 2. Specify filemode of the SOURCE disk (linked RR and accessed as): g LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL - DIR G R/W -- 4096 11 - - - 3. Specify filemode of the TARGET disk (linked R/W and accessed as): h LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL - DIR H R/W -- 40960 - - - 4. Activate Alternate Library with the following Copy commands: EAGALPRC MODULE G EAGRTPRC = H (REPLACE EAGRTALT MODULE G EAGRTLIB = H (REPlACE EAGALUME REPAMENG G EAGUME = H (REPLACE EAGALUME TXTAMENG G EAGUME = H (REPLACE Execute? Specify 1 (Yes), or 0 (Exit): 1 DMSNXD616W EAGRTPRC does not exist DMSMOD639E Error loading module EAGRTPRC, return code 11 from LOADMOD EAGACTAL: EAGRTPRC returned unexpected, RC=-4 So, this is sort of a bummer. It looks to me like EAGALPRC MODULE was, well, not actually transmitted correctly. It strikes me that this all could be avoided by simply providing the Alternate Library as a VMARC rather than a ZIP file. Would this be possible? Adam
Re: Rexx Alternate library
I remember there being an error in the install exec. On of the filemodes was incorrect, I think. I'll look back at my install and see if I can refresh my memory. On 8/8/07, Adam Thornton [EMAIL PROTECTED] wrote: EAGACTAL: Install and activate the Alternate Library 1. Verify if a REXX Runtime Library exists already: A REXX Runtime System does not exist. 2. Specify filemode of the SOURCE disk (linked RR and accessed as): g LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL - DIR G R/W -- 4096 11 - - - 3. Specify filemode of the TARGET disk (linked R/W and accessed as): h LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL - DIR H R/W -- 40960 - - - 4. Activate Alternate Library with the following Copy commands: EAGALPRC MODULE G EAGRTPRC = H (REPLACE EAGRTALT MODULE G EAGRTLIB = H (REPlACE EAGALUME REPAMENG G EAGUME = H (REPLACE EAGALUME TXTAMENG G EAGUME = H (REPLACE Execute? Specify 1 (Yes), or 0 (Exit): 1 DMSNXD616W EAGRTPRC does not exist DMSMOD639E Error loading module EAGRTPRC, return code 11 from LOADMOD EAGACTAL: EAGRTPRC returned unexpected, RC=-4 So, this is sort of a bummer. It looks to me like EAGALPRC MODULE was, well, not actually transmitted correctly. It strikes me that this all could be avoided by simply providing the Alternate Library as a VMARC rather than a ZIP file. Would this be possible? Adam -- Mark Pace Mainline Information Systems
Re: Rexx Alternate library
I can't find it now. But it was on EAGACTAL exec. I'm pretty certain it had something to do with the FileMode. I think it was copying it as H0 or H1 and needed to be H2, or something like that. -- Mark Pace Mainline Information Systems
Re: Rexx Alternate library
Filemode numbers normally don't play games with you, except: when storing files on 190 or 19E, the number should be 2, else the files are invisible after an IPL CMS And filemode 0 is -by default- invisible on R/O linked minidisks, but I saw you used an SFS dir. How did you upload the modules? It should be binary and most probably LRECL 1024, RECFM F and then you would need to execute COPYFILE (UNPACK on the uploaded files. It is namely impossible to transmit a binary fle as RECFM V files through the PC world where files have no recordlengths, therefore one must make these files RECFM F somehow, VMARC creates F80; COPYFILE PACK creates F1024. 2007/8/8, Adam Thornton [EMAIL PROTECTED]: On Aug 8, 2007, at 1:34 PM, Mark Pace wrote: I can't find it now. But it was on EAGACTAL exec. I'm pretty certain it had something to do with the FileMode. I think it was copying it as H0 or H1 and needed to be H2, or something like that. I changed it to be H2. No dice: listf * module h EAGRTPRC MODULE H2 EAGRTLIB MODULE H2 Ready; T=0.01/0.01 14:50:09 eagrtprc DMSMOD639E Error loading module EAGRTPRC, return code 11 from LOADMOD *I* think the problem is that the modules got corrupted during upload; FTP from systems which don't understand structured record formats tends to do that to me. A VMARC would make this just go away, I again hint strongly while clearing my throat in IBM's direction. Adam -- Kris Buelens, IBM Belgium, VM customer support
Re: Rexx Alternate library
The EXEC and the REDAME file might be able to survive a transfer, but then I'd expect a transfer with ASCII translation. The TEXT and TXTAMENG should surely be F80, a CEXEC with F2048 seems wrong: compiled execs are F1024; the REPAMENG should most probably be F80. But, I reapeat the MODULEs all mus be transferred in F and then made RECFM V, and the only easy way is COPYFILE (UNPACK, hence, they should be tranferred as F1024. 2007/8/8, Adam Thornton [EMAIL PROTECTED]: On Aug 8, 2007, at 2:17 PM, Kris Buelens wrote: Filemode numbers normally don't play games with you, except: when storing files on 190 or 19E, the number should be 2, else the files are invisible after an IPL CMS And filemode 0 is -by default- invisible on R/O linked minidisks, but I saw you used an SFS dir. How did you upload the modules? It should be binary and most probably LRECL 1024, RECFM F and then you would need to execute COPYFILE (UNPACK on the uploaded files. It is namely impossible to transmit a binary fle as RECFM V files through the PC world where files have no recordlengths, therefore one must make these files RECFM F somehow, VMARC creates F80; COPYFILE PACK creates F1024. Here are the commands in the ftpput.cmd file in the ZIP distribution. They are what I ran: quote type e quote mode b put EAGACTAL.EXEC put EAGRTALT.MODULE put MAKEALT.README put VALTLIB.REXXMOD put VALTLIB.SEXEC quote site fix 1104 put EAGALPRC.MODULE quote site fix 80 put EAGALUME.REPAMENG quote site fix 80 put EAGALUME.TXTAMENG quote site fix 2048 put VALTLIB.CEXEC quote site fix 80 put VALTLIB.TEXT quit I find the 1104 suspicious, and the lack of recl on the first several also suspicious, particularly since the EAGACTAL EXEC thus transmitted was useless. Adam -- Kris Buelens, IBM Belgium, VM customer support
Re: Rexx Alternate library
On Aug 8, 2007, at 3:20 PM, Kris Buelens wrote: The EXEC and the REDAME file might be able to survive a transfer, but then I'd expect a transfer with ASCII translation. The TEXT and TXTAMENG should surely be F80, a CEXEC with F2048 seems wrong: compiled execs are F1024; the REPAMENG should most probably be F80. But, I reapeat the MODULEs all mus be transferred in F and then made RECFM V, and the only easy way is COPYFILE (UNPACK, hence, they should be tranferred as F1024. I'll try that. However, in that case, the documentation needs to be fixed, as it's clearly broken as delivered. And, really, a VM-friendly packaging system would be much better. Adam
Re: Rexx Alternate library
On Aug 8, 2007, at 2:17 PM, Kris Buelens wrote: Filemode numbers normally don't play games with you, except: when storing files on 190 or 19E, the number should be 2, else the files are invisible after an IPL CMS And filemode 0 is -by default- invisible on R/O linked minidisks, but I saw you used an SFS dir. How did you upload the modules? It should be binary and most probably LRECL 1024, RECFM F and then you would need to execute COPYFILE (UNPACK on the uploaded files. It is namely impossible to transmit a binary fle as RECFM V files through the PC world where files have no recordlengths, therefore one must make these files RECFM F somehow, VMARC creates F80; COPYFILE PACK creates F1024. Alas (after retransferring the files at F 1024) copyfile eagalprc module g eagrtprc = h (unpack replace DMSCPY068E Input file EAGALPRC MODULE G1 not in packed format Adam
