DIGITS was what I couldn't remember.  Thank you.

Had to use the RIGHT when trying to stuff an INT into a CHAR(6) required by RLSJOBSCDE  JOB(...) ENTRYNBR(here)

Otherwise I was getting all zeros.

just curious - do you have jobs in the job scheduler with the same name ? If not, the entry number isn't required if you accept the default as *ONLY. Also, and just in case you are not aware - this sql service can be used to work with your scheduled jobs qsys2.scheduled_job_info and consumed into your program if that makes life easier for you...(now or in the future). Thanks

DIGITS was what I couldn't remember.  Thank you.

Had to use the RIGHT when trying to stuff an INT into a CHAR(6) required by RLSJOBSCDE  JOB(...) ENTRYNBR(here)

Otherwise I was getting all zeros.

Rich:

Part 1:

Job        
BRMMAINT   
BRMRECOVER 
BRMREORG   
BRMSSTATUS 

Part 2:

...

          DECLARE BRM CURSOR FOR
            select SCHEDULED_JOB_NAME, SCHEDULED_JOB_ENTRY_NUMBER
            FROM QSYS2.SCHEDULED_JOB_INFO
            WHERE SCHEDULED_JOB_NAME LIKE 'BRM%'
              AND STATUS = 'HELD';

...

          -- WRKJOBSCDE BRM*
          -- Release any which are held
          SET END_TABLE = 0;
          OPEN BRM;
          FETCH BRM INTO JOBNAME, JOB_ENTRY_NBR;
          WHILE END_TABLE = 0 DO
             SET JOB_ENTRY_NBR_CHAR = LPAD(JOB_ENTRY_NBR, 6, '0');
             SET COMMAND = 'RLSJOBSCDE JOB(' concat JOBNAME concat
                ') ENTRYNBR(' concat JOB_ENTRY_NBR_CHAR concat ')';
             CALL QSYS2.QCMDEXC(COMMAND);
             FETCH BRM INTO JOBNAME, JOB_ENTRY_NBR;
           END WHILE;
           CLOSE BRM;

...

just curious - do you have jobs in the job scheduler with the same name ? If not, the entry number isn't required if you accept the default as *ONLY. Also, and just in case you are not aware - this sql service can be used to work with your scheduled jobs qsys2.scheduled_job_info and consumed into your program if that makes life easier for you...(now or in the future). Thanks

DIGITS was what I couldn't remember.  Thank you.

Had to use the RIGHT when trying to stuff an INT into a CHAR(6) required by RLSJOBSCDE  JOB(...) ENTRYNBR(here)

Otherwise I was getting all zeros.

Based on the above, I don't believe you need entry number since you don't have duplicate job names. Since the job name is unique, you should be able to just use *ONLY (which is the default) ....I can see if you had duplicate job names then yes, the entry number is required but that doesn't seem to be the case. I was just curious as to why you were needing the entry number....glad its working for you though. Rich

Rich:

Part 1:

Job        
BRMMAINT   
BRMRECOVER 
BRMREORG   
BRMSSTATUS 

Part 2:

...

          DECLARE BRM CURSOR FOR
            select SCHEDULED_JOB_NAME, SCHEDULED_JOB_ENTRY_NUMBER
            FROM QSYS2.SCHEDULED_JOB_INFO
            WHERE SCHEDULED_JOB_NAME LIKE 'BRM%'
              AND STATUS = 'HELD';

...

          -- WRKJOBSCDE BRM*
          -- Release any which are held
          SET END_TABLE = 0;
          OPEN BRM;
          FETCH BRM INTO JOBNAME, JOB_ENTRY_NBR;
          WHILE END_TABLE = 0 DO
             SET JOB_ENTRY_NBR_CHAR = LPAD(JOB_ENTRY_NBR, 6, '0');
             SET COMMAND = 'RLSJOBSCDE JOB(' concat JOBNAME concat
                ') ENTRYNBR(' concat JOB_ENTRY_NBR_CHAR concat ')';
             CALL QSYS2.QCMDEXC(COMMAND);
             FETCH BRM INTO JOBNAME, JOB_ENTRY_NBR;
           END WHILE;
           CLOSE BRM;

...

just curious - do you have jobs in the job scheduler with the same name ? If not, the entry number isn't required if you accept the default as *ONLY. Also, and just in case you are not aware - this sql service can be used to work with your scheduled jobs qsys2.scheduled_job_info and consumed into your program if that makes life easier for you...(now or in the future). Thanks

DIGITS was what I couldn't remember.  Thank you.

Had to use the RIGHT when trying to stuff an INT into a CHAR(6) required by RLSJOBSCDE  JOB(...) ENTRYNBR(here)

Otherwise I was getting all zeros.

This would be an easier solution:

use straight LPAD , doesn't even require casting, it accepts multiple types.

------------------------------
--ft
------------------------------

varchar format should also work.

values VARCHAR_FORMAT(1037, '099999999999999999') ;

I usually use to add a comma in large numbers i.e.

VARCHAR_FORMAT(LargeNumber, '999G999G999G999G999G999')