RE: RCLSTG

Interesting. I have a system where there were damaged IBM cross reference files. We ran a 'full RCLSTG' over the weekend, and I still have damaged IBM cross reference files. I've never before had those after the RCLSTG, but I usually only run the RCLSTG *DBXREF. I think I'll try only that one and see what happens.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, February 18, 2011 4:23 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RCLSTG

IBM is really discouraging me from running a full RCLSTG as a general
habit. Every other month, when we perform scheduled maintenance, we run
the full RCLSTG. Apparently if that has any abnormalities then the part
of it that does a RCLSTG *DBXREF may not behave and you could get results
like:

02/11/11 20:55 - RCLSTG with no options
02/11/11 21:05 - MCH3402, CPF9999
02/11/11 21:07 - ..
02/11/11 21:10 - ..
02/11/11 21:20 - ..
02/11/11 22:24 - MCH2601, CPF9999, SYSTXTINDXSYSTE00001
02/11/11 22:36 - MCH3402, CPF9999
02/11/11 22:51 - ..
02/11/11 22:59 - ..
02/11/11 23:02 - ..
02/11/11 23:03 - ..
02/11/11 23:06 - MCH3603, CPF3698, CPF9999
02/11/11 23:38 - MCH3402, CPF9999
02/12/11 00:11 - ..
02/12/11 01:00 - ..
02/12/11 01:31 - MCH3603, CPF3698, CPF9999
02/12/11 01:57 - MCH3402, CPF9999
02/12/11 02:02 - MCH3603, CPF3698, CPF9999
02/12/11 02:24 - MCH3402, CPF9999
02/12/11 02:37 - ..
02/12/11 02:38 - ..
02/12/11 02:46 - ..
02/12/11 02:53 - MCH3603, CPF3698, CPF9999
02/12/11 03:00 - MCH3402, CPF9999
02/12/11 03:45 - CPC2206, CPF327E, CPF7304, SQL0601, MCH2601, CPF2499,
CEE3201, CEE9901
02/12/11 06:53 - CPCA08C, CPCA08C, CPCA08C, CPCA08C, CPC2192, ...
02/12/11 06:56 - CPC8208, RCLSTG processing complete. 2807086 objects
processed. 13 deleted.
02/12/11 06:56 - SAVSYS
02/12/11 07:04 - SAVLIB LIB(*NONSYS)
02/12/11 07:04 - MCH2601, SYSTXTINDXSYSTE00001.CPF3741
02/12/11 07:05 - 259 objects saved from QSYS2. 1 not saved.
02/12/11 11:14 - 761 libraries saved, 1 partially saved, 0 not saved.

Apparently running a RCLSTG *DBXREF after a full RCLSTG is not a bad idea.
Even though the full RCLSTG does a RCLSTG *DBXREF. Just the *DBXREF runs
in a short amount of time. Can't get a feel from them if signing off/on
may clear some of the messages and affect the *DBXREF, like, maybe some
programmer didn't handle memory allocations well or some such thing.

I have a pmr on this, but I don't think it's going anywhere.

Rob Berendt