On 16-Oct-2015 11:41 -0500, James H. H. Lampert wrote:
I wrote:
Here's something I've never seen before:

I went to do a STRDBG, and it immediately threw a CPD0162
Parameters do not match those in program QTECNTDB in QSYS.

Has anybody ever seen anything like this before?

Yes, typically as the result of improper System Change Management. The /same customization/ that was performed on a prior level of maintenance has to be repeated after any new maintenance is applied [and that maintenance impacts whatever was customized].

A Google search gave me a clue: it seems this particular customer
box has another STRDBG command, in a library called QSYSDPS, ahead of
QSYS (?!!) in the library list.

Qualifying my STRDBG command took me right into the debugger. But
that kind of begs the question, what is this QSYSDPS/STRDBG, why does
it LOOK just like the real thing, and what could it possibly be doing

Presumably at some point in the past [and the DSPOBJD QSYSDPS/STRDBG *CMD *FULL OUTPUT(*PRINT), DSPOBJD QSYSDPS/STRDBG *CMD *SERVICE OUTPUT(*PRINT), and DSPCMD QSYSDPS/STRDBG OUTPUT(*PRINT) collected *before* any other /change/ activity, might help to reveal when\what; e.g. any changes that might intend to resolve\circumvent the error] the following scripted change was performed, but that same script was not repeated when required; i.e. the following probably was required to be repeated, but was not performed again, after the most recent upgrade to the OS:

chgcmddft QSYSDPS/STRDBG ...

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].