Re: SQL Stored Procedure Strangeness

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/27/2018
10:42:25 AM:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/26/2018
08:10:11 PM:

Are you sure about what's being run or where the error is?

I noticed a different in the names..
Null values not allowed for parameter 4 in procedure IMLFRESTOR

Specific IMLFRSTSP

IMLFRESTOR is the CL procedure name -- same as the CL program
name.

Thanks, Charles. That was the problem -- as shown by this new
joblog I created today. I added SNDPGMMSG today so I could see what was
being passed to the RUNSQL command. The second CL is calling the wrong
stored procedure name. I apparently fixed the first CL (to call the
correct stored procedure name) after I had already copied the first source
member to the second source member.

IMLFbackup TYPE(IMLFBACKUP) TABLE(*dtl) COMPANY(*RGN03)

CALL IM_LIFO_BACKUP ( 'IMLFBACKUP', '*DTL', '*RGN03', NULL )
Object LFDTL00307 in IMLFBACKUP type *FILE deleted.
Object LFDTL00307 in IMLFBACKUP type *FILE created.
1 objects duplicated.
Object LFDTL00322 in IMLFBACKUP type *FILE deleted.
Object LFDTL00322 in IMLFBACKUP type *FILE created.
1 objects duplicated.
Object LFDTL00344 in IMLFBACKUP type *FILE deleted.
Object LFDTL00344 in IMLFBACKUP type *FILE created.
1 objects duplicated.
Backup completed.
Backup completed.

IMLFrestor TYPE(IMLFBACKUP) TABLE(*dtl) COMPANY(*RGN03)

CALL IMLFRESTOR ( 'IMLFBACKUP', '*DTL', '*RGN03', NULL )
Null values not allowed for parameter 4 in procedure IMLFRESTOR in *N.
RUNSQLSTM or RUNSQL command failed.
SQL9010 received by procedure IMLFRESTOR. (C D I R)


Sincerely,

Dave Clark