Re: RUNSQLSTM drop/create alias error

CPF327E will mention RCLSTG, but not for RC2 [return code 2] which is _expected_ prior to a SQL0601. Either the DROP should remain in the script [what is given shows it is commented with '--'] and ERRLVL(30) be used, or the CREATE ALIAS should also be commented\removed from the script. The RC2 suggests to delete the file IMPACT in library TRSFDD [or choose a unique name; reiterated in the SQL0601], if the CREATE is intended to ignore the error. Or ERRLVL(31) could be used to ignore the -601 condition, but that would likely be ignoring too much in a script.

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/sqlp/rbafyexecutestmt.htm

If RC3 for CPF327E, do one of the following for recovery, but best only *after* doc collection to assist determining origin [open a PMR with IBM]:

RCLSTG SELECT(*DBXREF) /* restricted state required */
RCLDBXREF /* prompt for parms; not on older releases */
CALL QDBXRCTX /* I do not recall parms; search internet */

Regards, Chuck

Frances Denoncourt wrote:

I had a sql stmt that ran just fine until this afternoon. It worked
all morning just fine. I think it started aborting when I deleted the
file, made mods, recreated it.

Found something about RCLSTG - not something I'll be doing or asking
OPS. I tried using a different alias. Didn't work.

How do you even view a list of aliases for a file? We don't have a
SQL - cannot STRSQL, but can RUNSQLSTM using a source file.

Spent a couple of hours trying to track this down. Your help would
be greatly appreciated. Thanks, Fran


RUNSQLSTM SRCFILE(TRSFDD/SQLSRC) SRCMBR(UPDATEIMP) COMMIT(*NONE) Alternative name for file IMPACT not allowed.
File IMPACT not created in library TRSFDD.
IMPACT in TRSFDD type *FILE already exists. RUNSQLSTM command failed. RUNSQLSTM command failed.

After the 'already exists' I tried this:

*************** Beginning of data ***************
--drop alias trsfdd/impact;
Create alias trsfdd/Impact FOR TRLIBDTA/TRIMPCP ;
UPDATE trsfdd/Impact set PCPROC = ' ';