progam change date updated for SQLRPGLE program
25 pts.
0
Q:
progam change date updated for SQLRPGLE program
Can anyone tell me where I can fird the reason that the 'program last change date' is updated in an SQLRPGLE program when it is run?  It showed up on an audit and the auditors say it is unacceptable.  I am looking for proof that this the way it is from some kind of official source, or a way to compile the programs so this does not happen.  Our other option is to rewrite all of our sqlrpgle programs

Software/Hardware used:
I-series, SQLRPFLE
ASKED: Oct 2 2009  7:21 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
8025 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
I cannot find a program last change date field.

Are you saying in DSPOBJD the
Change/Usage information:
Change date/time . . . . . . . . . . : 09/30/09 10:27:08

Was changed on a program object when it was run?

Or is this some other command/other field of data?

Phil

=============
I don't have a lot for you -- perhaps someone else ...

search400.techtarget.com/.../0,289625,sid3_gci1333251,00.html

or

Perhaps the first time used after conversion to v6r1???

http://74.125.95.132/search?q=cache:JgEhx2p9J2IJ:www.mysiriuszone.com/component/option,com_docman/task,doc_download/gid,2736/Itemid,484/+as/400+%22change+date%22+rpgle+sql&cd=49&hl=en&ct=clnk&gl=us

Phil

===============================================
For any program with embedded SQL, the first thing to check is if the SQL access plan was automatically updated. Use the PRTSQLINF command against the program to see SQL internal info. If the access plan was updated, message SQL4021 should show date/time of the latest access plan update in the printed output. See if that matches up with the *PGM object header.

Tom
Last Answered: Oct 7 2009  11:32 PM GMT by TomLiotta   8025 pts.
Latest Contributors: Philpl1jb   24610 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Sodafountain   25 pts.  |   Oct 2 2009  8:34PM GMT

Yes the Change date/time field is changing.
As far as we can tell it is changing when it is run. It seems to be only occuriring in programs in which the embedded SQL statements are actually updating a file

 

Whatis23   4040 pts.  |   Oct 2 2009  8:48PM GMT

That may unfortunately be the reason. We had a similiar experience with an auditor where a program was “updated” because of a QMQRY statement inserting the new date daily.

 

Satsho   1235 pts.  |   Oct 5 2009  8:59PM GMT

I am not sure how the Change date/time will change whenever the progam is called. The last used date is used for that information.

How is this program called ?

 

Satsho   1235 pts.  |   Oct 5 2009  9:04PM GMT

I am not sure how the

 

Satsho   1235 pts.  |   Oct 5 2009  9:29PM GMT

Ok, found some info on IBM’s site

The following options cause the Change Date/Time field on the DSPOBJD display to be updated:

- CHGOBJAUD
- CHGOBJD
- CHGOBJOWN
- CHGOBJPGP
- EDTOBJAUT (when authority to *PUBLIC is changed)
- GRTOBJAUT (when authority to *PUBLIC is changed)
- MOVOBJ
- RNMOBJ
- Restore operations

The following options are specific to *LIB objects and cause the Change Date/Time field on the DSPOBJD display to be updated:

- Re-creating an object into the library
- Renaming an object in the library
- Moving an object from/to the library
- Deleting an object in the library
- Changing the library with the CHGOBJD, CHGLIB, CHGOBJAUD, CHGOBJOWN, CHGOBJPGP cmds

The following options are specific to *PGM objects and cause the Change Date/Time field on the DSPOBJD display to be updated:
- Compressing or decompressing a *PGM object with the CPROBJ or DCPOBJ commands.
- Using CHGPGM , except when message CPC0541- No change required is received.
- Using UPDPGM . This is applicable only to ILE programs.

Also refer to SUG APAR SE18894 for additional information.

So, you may need to change your process accordingly…

 

Sodafountain   25 pts.  |   Oct 6 2009  5:14PM GMT

We think it is because the SQL has some dynamic elements that are changed as it is run. They are called from CL programs, so we are going to try copying thme to qtemp and then running them from there so the object in the production library will not change

 

0