Never got a response on CMSPIP-L, so I'll try here:
Okay I'm trying to build the segment PIPERLD and am stuck on step 2: 1. Now, you must create the files necessary to actually build and define the logical segment and DCSS. Every object that can be built by the VMFBLD exec must have a build list. In this case, I copied the PIPERLD EXC00000 build list from the one used to build CMSPIPES and modified it for my use. The following is my PIPERLD EXC00000 build list: :FORMAT. 2 :OBJNAME. PIPERLD.SEGMENT :BLDREQ. CMSMLOAD.PIPELINE.MODULE MMMBL493.PIPES+.LSEG :OPTIONS. LOADFUNC(LSEG PIPES+) :EOBJNAME. Be sure to match the EXEC used to build CMSPIPES at your level of CMS. In CMS 13, for example, CMSPIPES is built by DMSSBPIP EXEC, which includes RXSOCKET in the CMSPIPES segment. For CMS 13, PIPERLD EXC00000 might look like this: :FORMAT. 2 :OBJNAME. PIPERLD.SEGMENT :BLDREQ. CMSMLOAD.PIPELINE.MODULE CMSMLOAD.RXSOCKET.MODULE MMMBL493.PIPES+.LSEG DMSBL493.RXSOCKET.LSEG :OPTIONS. LOADFUNC(LSEG PIPES+) LOADFUNC(LSEG RXSOCKET) :EOBJNAME. The second thing to be built is PIPES+ LSEG, the file that defines the logical segment. The contents should be as follows: MODULE PIPELINE ( SYSTEM SERVICE IMMCMD NAME PIPMOD Both files should go on the local mod disk (3C4, accessed at mode E). 2. Defining PIPERLD in PPF: I cannot seem to find a any CMSPIPES build list. list cmspipe* * * CMSPIPES PSEGMAP D5 list dmssb* * * DMSLST002E File not found q cplevel z/VM Version 5 Release 4.0, service level 0801 (64-bit) Generated at 12/12/2008 11:02:41 CDT IPL at 06/29/2009 12:16:01 CDT Ready; T=0.01/0.01 11:51:37 q cmslevel CMS Level 24, Service Level 801 Ready; T=0.01/0.01 11:51:39 TIA, Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76710 _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.