MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

Re: Checking object create dates



fixed

On 14-Feb-2014 12:12 -0800, CRPence wrote:
<<SNIP>> the Change Object Description (QLICOBJD) API exists to
update the object and the Replace Command Exit Program (QCARPLCM) API
[enhanced to have a *AFTER invocation] exists to effect the change
for the usage of the CRTDUPOBJ command.

I forgot to include the link to the enhancement details; that and a snippet:
<https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/CL%20retrieve%20exit%20programs%20can%20run%20after%20command%20completion>
_CL retrieve exit programs can run after command completion_
Updated February 17, 2012 by ScottForstie
"The IBM i operating system supports two exit points for control language (CL) commands: QIBM_QCA_CHG_COMMAND and QIBM_QCA_RTV_COMMAND. For each regular CL command, and proxy CL commands in the QSYS library, one exit program can be registered for the CHG exit point and up to ten exit programs can be registered for the RTV exit point.

The IBM i command analyzer support for the QIBM_QCA_RTV_COMMAND exit point has been enhanced via PTFs for V5R4 (SI45987), 6.1 (SI45986), and 7.1 (SI45985) releases.

Before the PTF, the registered exit programs were always called just before control was transferred to the command processing program (CPP) associated with the command being run. After the PTF is applied, you will be able to register an exit program for the QIBM_QCA_RTV_COMMAND exit point and indicate that you want the exit program to be called after control returns from the CPP.
..."

The following is a link to the Command Analyzer Change Exit Program with Exit Point Name: QIBM_QCA_CHG_COMMAND and Exit Point Format Name: CHGC0100 ... also for reference:
<http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/apis/xcachg.htm>






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact