Graham,

One other thought.  When you are editing the JCL member, on the ISPF Command
line enter HILITE

This function will hilite the data in the member according to certain rules.
JCL is one such rule.  I also use on the right hand side 3 in the COLORING
section and place a slash in the next entry for parentheses matching as
well.  The following example may not be for your level of the operating
system (i.e. ISPF level)



File  Languages  Colors  Help
----------------------------------------------------------------------------
--
                             Edit Color Settings
Command ===> (this menu shows up when you type "hilite")

Language:    1. Automatic     Coloring:     1. Do not color program
             2. Assembler                   2. Color program
             3. BookMaster                  3. Both IF and DO logic
             4. C                           4. DO logic only
             5. COBOL                       5. IF logic only
             6. IDL 
             7. ISPF DTL         Enter "/" to select option
             8. ISPF Panel           Parentheses matching
             9. ISPF Skeleton     /  Highlight FIND strings
            10. JCL               /  Highlight cursor phrase
            11. Pascal  
            12. PL/I             Note: Information from this...
            13. REXX             saved in the edit profile.

F1=Help    F2=Split      F3=Exit    F7=Backward F8=Forward 
F9=Swap    F10=Actions  F12=Cancel


There is a lot of rule types you can use to Hilite.  The above list is only
partial.


Lizette



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Graham Hobbs
Sent: Tuesday, April 30, 2013 5:06 PM
To: [email protected]
Subject: Compile COBOL/CICS pgms on z/OS problem

Hello,
Back again. Am at Dallas IIC z/OS, compiling a dozen COBOL/CICS pgms all
having a SIZE problem. The following JCL almost worked without SIZE:

//ACICSP01 JOB (CONRAD-C),'IBMUSE2',CLASS=A,MSGCLASS=0,MSGLEVEL=(1,1)

//MYLIBS   JCLLIB ORDER=(DFH420.CICS.SDFHPROC)                 
//QKVSP01  EXEC PROC=DFHZITCL,
//    INDEX=DFH420.CICS,                                       
//    LNGPRFX=IGY420,                                          
//    DSCTLIB=IBMUSE2.QKVS,                                    
//    PROGLIB=VENDOR.LINKLIB.SECOND)                           
//COBOL.SYSIN  DD DSN=IBMUSE2.QKVS(QKVSP01),DISP=SHR           
//LKED.SYSLMOD DD DSN=VENDOR.LINKLIB.SECOND(QKVSP01),DISP=SHR  

.. but all compiles give ..

IGYOS4013-W   The SIZE(MAX) option was specified together with the SQL or
CICS option.  SIZE(nnnnn) option is recommended, where nnnnn is an explicit
size value (not MAX) that leaves enough storage in the user region for the
DB2 coprocessor or CICS integrated translator services.

.. onto solutions .. goggling says use SIZE=4000K; tried various combos,
closest I got was with ..

QKVSP01  EXEC PROC=DFHZITCL,PARM=(SIZE=4000K,    
    INDEX=DFH420.CICS,                           
    LNGPRFX=IGY420,                              
    DSCTLIB=IBMUSE2.QKVS,                        
    PROGLIB=VENDOR.LINKLIB.SECOND)               

.. but this gave ..

 STMT NO. MESSAGE                                             
        3 IEFC624I INCORRECT USE OF PERIOD IN THE PARM FIELD

.. so tried .. 

QKVSP01  EXEC PROC=DFHZITCL,        
    SIZE=4000K,                     
    INDEX=DFH420.CICS,              
    LNGPRFX=IGY420,                 
    DSCTLIB=IBMUSE2.QKVS,           
    PROGLIB=VENDOR.LINKLIB.SECOND

.. and got

STMT NO. MESSAGE

       3 IEFC001I PROCEDURE DFHZITCL WAS EXPANDED USING PRIVATE LIBRARY
DFH420.CICS.SDFHPROC   
       3 IEFC657I THE SYMBOL SIZE WAS NOT USED

Can anyone say where am wrong, how to specify a SIZE=4000K parm? Am guessing
I am simply placing or coding SIZE slightly incorrectly .. very frustrating.
Again, please, thanks
Graham Hobbs

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to