Well, HLASM is a separately orderable and rather expensive Licensed Program Product. If you did not order it, it won't be on you tape.
You _may_ be able to Assemble it using and older assembler after some source code changes. Or, you might consider purchasing a much less expensive ISV HLASM-compatible assembler (ask if you are interested, I have the name at work). Also, while RSCS is shipped and installed, AFAIK use of anything other than the LPR printer line drivers requires a paid up license for the full RSCS product. Off the top of my head (again, details at work), any IBM product that need to be ENABLED (usually done in SYSTEM CONFIG) requires a specific product license (aside from the RSCS LPR printer line drivers?). You'd think it wouldn't be that hard to include a "bright neon" warning about license requirements in the doc for the command that ENABLEs the product. Mike Walter Hewitt Associates (Sent from the wee keyboard on a Blackberry.) ----- Original Message ----- From: Steve Harman [[email protected]] Sent: 05/05/2009 04:17 PM EST To: [email protected] Subject: I need to assemble RSCS exits I'm a newbie. I know next to nothing about VM, so please understand my = goofy questions are not from laziness, it's sheer ignorance on my part. I am the primary vm sysprog at our site, or I'd go ask our experienced = person. We have a vm 5.2 system (yes, now unsupported) running RSCS v3.2. I've = been told that we need to be off the old release of RSCS by the end of Ju= ne or we'll incur a monthly fine. RSCS is now packaged with the base OS. I've ordered and sort of installe= d VM5.4 on a 2-lvl guest system. I will not have it to a point where I can= put it on our production system before the end of June because of my inexperience. I feel safer running on an unsupported version than trying= to migrate 5.4 before I'm ready. IBM has offered some suggestions on getting the FL540 version of RSCS fro= m the 2-lvl guest to our production system. One thing I need to do is assemble some exits and rebuild the RSCS loadlib using the FL540 maclibs.= I sent the source assemble files, the lkedctrl file, and a cntrl file to = the 5.4 system's 5vmrsc40 191 disk. To most of you, I'm sure that sounds simple. I've been going through the= RSCS ProgDir trying to figure out how to assemble exits and rebuild the = load lib. The problem is, when I try to do a VMFHLASM command as shown i= n the example, it fails because it can't find HLASM MODULE. I browsed the = VMFHLASM exec and it calls VMFASM EXEC. Looks like it falls thru looking= for HLASM MODULE because it can't find ASMAHL MODULE. I guess we don't have the hi-lvl assembler, it must be a cost feature. = Seems like ProgDir shouldn't use it in the examples. So, I found the CMS assemble command. After a little trial and error, I = got one of the exits to assemble (with a few IFO012 errs, haven't figured= that out yet). I had to do a 'global maclib DMTMACV3 GCTGPI HCPGPI HCPOM1 DMSGPI DMSOM' = to get what I think are the required macro libs. Am I headed in the right direction, or am I wasting a lot of my time? If= I get my exits assembled, how do I get the FL540 RSCS to hook them in? = Thanks for any suggestions. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
