Checking for uncommitted changes

[bvining@xxxxxxxxxxxx]

Walden,

NOT a formal programming interface (ie, it can change from release to
release and/or NLV (National Language Version) to NLV), but:

    DSPJOB OUTPUT(*PRINT) OPTION(*CMTCTL)

followed by a CPYSPLF to a file should provide the information you need.

All files currently under commitment control will be listed, along with
a column indicating the number of pending changes for each file.

The information is repeated for each active commitment definition for the job.

We have not heard requests in this area previously, but will consider
adding an indicator to the QTNRCMTI API (no promises though).

Bruce Vining

>
>I need a way to look for uncommitted changes in a job.
>
>I have looked into the Retrieve Commitment Information (QTNRCMTI) API, but
>this doesn't seem to help me. All I need to know is if there are any
>uncommitted changes, I don't care what files they are in or how many there
>are -- of course I won't complain if I get this info.
>
>For now I have resorted to checking for locks held by this job and assuming
>that if there are locks there are uncommitted changes and if there are not
>job locks there are not uncommitted changes. However this is somewhat fishy,
>I would like a better way.
>
>Anyone have any good ideas? (Or even any bad ideas)
>
>-Walden
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---