Home > IT Answers > AS/400 > CPD0304 when using SUBR and ENDSUBR in CLLE
JamesR
90 pts.
 CPD0304 when using SUBR and ENDSUBR in CLLE
CALLSUBR, CLLE, ENDSUBR, SUBR
I know I've run into this the past, but I can't remember the fix.  I am using V5R4 and trying to use CALLSUBR in my CLLE.  I end my mainline with a RETURN, then I have a SUBR/ENDSUBR... and a 2nd SUBR/ENDSUBR.. then a ENDPGM.  When the compiler hits the 2nd SUBR I get a CPD0304 and it rejects any commands following.  The QCPFMSG message file shows this for CPD0304



 Message . . . . :   SUBR command not allowed.                                 Cause . . . . . :   A SUBR command was specified inside a subroutine.         Recovery  . . . :   Either remove the SUBR command, or add an ENDSUBR command to close the previous subroutine before the SUBR command, and then try compiling the CL procedure again.                       
                   



Software/Hardware used:
iSeries, V5R4, CLLE
ASKED: October 27, 2009  4:10 PM
UPDATED: October 28, 2009  9:08 PM
RELATED QUESTIONS
Answer Wiki:
Here is a link that should help you. http://publib.boulder.ibm.com/infocenter/iadthelp/v7r0/index.jsp?topic=/com.ibm.etools.iseries.langref2.doc/subrc.html And here is the 2nd level text for your error Message ID . . . . . . . . . : CPD0304 Message file . . . . . . . . : QCPFMSG Library . . . . . . . . . : QSYS Message . . . . : SUBR command not allowed. Cause . . . . . : A SUBR command was specified inside a subroutine. Recovery . . . : Either remove the SUBR command, or add an ENDSUBR command to close the previous subroutine before the SUBR command, and then try compiling the CL procedure again.
Last Wiki Answer Submitted:  October 27, 2009  4:46 pm  by  CharlieBrowne   32,905 pts.
All Answer Wiki Contributors:  CharlieBrowne   32,905 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

I checked out the link… no help.

JamesR
 90 pts.
 

Here are snipets of the code:

ENDPROC:                             
                                     
             RETURN                  
                                     
/* ==================================
             SUBR       SUBR(FTP)    

                                           
             ENDSUBR                       
/* ========================================
             SUBR       SUBR(SWAPLIBL)     


When it hits SWAPLIBL is fails

And I end with:

ENDSUBR
/* =========================================

ENDPGM: ENDPGM 


Thanks!
JamesR
 90 pts.
 

What statements immediately precede the ENDSUBRs?

Tom

TomLiotta
 108,240 pts.
 

I am doing pretty much the same thing you are. Here is my code.


 /*********************************************************************/ 
 /* STOP THE SUBROUTINES FROM BEING EXECUTED AT PROGRAM END.          */ 
 /*********************************************************************/ 
                                                                         
        GOTO       CMDLBL(ENDCLPGM2)                                     
                                                                         
 /*********************************************************************/ 
 /* SUBROUTINE TO SUBTRACT A NUMBER OF DAYS FROM THE DATE.            */ 
 /*********************************************************************/ 
                                                                         
            SUBR       SUBR(GETDATE)                                     
                                                                         
              CALLPRC    PRC(SUBDAYSR) PARM((&DATE#) (&DAYSTOSUB)) +     
                           RTNVAL(&DATE#)                                
                                                                         
              ENDSUBR        
/*********************************************************************/ 
/* SUBROUTINE TO CONVERT DATE TO B&L FILE FORMAT.                    */ 
/*********************************************************************/ 
                                                                        
           SUBR       SUBR(CONVRTDATE)                                  
                                                                        
             CALLPRC    PRC(RTVBLFILDT) PARM((&DATE#)) +                
                          RTNVAL(&CHKDATE#)                             
                                                                        
                                                                        
             ENDSUBR                                                    
                                                                        
ENDCLPGM2:                                                              
ENDPGM

The only thing I can see different between yours and mine is the Return statement. What happens if you take it out?

Teandy
 5,830 pts.
 

When I take out the RETURN statement I get the same error.

Tom… look at my last post… you will see I have a TAG and a RETURN.

JamesR
 90 pts.
 

JamesR:

In the code that I can see, there are no statements shown between the two SUBR and ENDSUBR sections — the subroutine statements are snipped out. What statements immediately precede the two ENDSUBRs?

Tom

TomLiotta
 108,240 pts.
 

As I posted earlier:

ENDPROC:

RETURN

/* ==================================
SUBR SUBR(FTP)
…
ENDSUBR
/* ========================================
SUBR SUBR(SWAPLIBL)
…
ENDSUBR
/* =========================================

ENDPGM: ENDPGM

JamesR
 90 pts.
 

I FOUND IT! It was caused by an unmatch DO statement in the SUBR before the SUBR it failed on…. this is what I had in SUBR FTP:

RTVMBRD    FILE(RVUXCEL) NBRCURRCD(&RCDCNT)                
MONMSG     MSGID(CPF0000) EXEC(DO)                         
IF         COND(&RCDCNT *EQ 0) THEN(DO)                    
   CHGVAR  VAR(&MSG60) VALUE('The uploaded file is empty') 
   CHGVAR VAR(&ERRCODE) VALUE('1002')                      
   RTNSUBR                                                 
ENDDO

There was an error message about it but it was buried in all the other error message it caused. Thanks for your help all!

JamesR
 90 pts.
 

I’m glad you found it because you still didn’t show what was immediately before the two ENDSUBRs. Without knowing the code that comes before the ENDSUBRs, it’s difficult to see something like a missing ENDDO.

Another possiblity is that MONMSG might have been before the ENDSUBR. IBM released a PTF for that one.

/* ==================================
             SUBR       SUBR(FTP)    
                                        <-- here is immediately before ENDSUBR
             ENDSUBR

Usually, just the single command before the ENDSUBR is enough to know the solution. BTW, was there no “mismatched DO-ENDDO” error message? What severity was on the message if one was sent?

Tom

TomLiotta
 108,240 pts.