Re: QZDASOINIT file update question.

Well - to prepare for the next time, when someone accuses a "program" to do something wrong, you could add some audit columns to your table(s).

For example:
column client_ip varchar(128) generated always as (sysibm.client_ipaddr),
column client_host varchar(128) generated always as (sysibm.client_host)

These would also be populated when the SQL is executed form a program on the machine itself - then with the IP and hostname of your machine.

As client programs normally only update explicitly named columns, it will not break your client apps - but of course you maybe have to check and recompile your programs.

HTH
Daniel

Am 29.03.2025 um 19:10 schrieb Marc Rauzier <marc.rauzier@xxxxxxxxx>:

Le 29/03/2025 à 18:46, Robert Rogerson a écrit :

Thanks Patrik and Daniel,

<rant> I was called into a meeting yesterday at 4pm which lasted 3 hours.
I showed the PC guys the journal records that (I believe) show clearly that
the external programs from the sp create the order and then add items to
the order but an external program does not change the order status from 'T'
to blank. An external QZDASOINIT job does therefore a .Net job. The PC
guys said it wasn't them. In the end I agreed to change the external
program on the add items sp. So here I am working on a Saturday changing a
program that I don't believe needs to be changed because (I believe) they
can't find what's updating the IBMi.
</rant>

You might find the IP address of the remote device which performed the update with *TYPE5 information provided by DSPJRN command.

https://www.ibm.com/docs/api/v1/content/ssw_ibm_i_75/rzaki/rzakifixlength.htm

----

305 Address family (JOADF, Address_Family) Char (1) The address family identifies the format of the remote address for this journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then 0 will be returned for the address family.

The possible values are:

* *0* = This entry was not associated with any remote address.
* *4* = The format of the remote address is Internet protocol version 4.
* *6* = The format of the remote address is Internet protocol version 6.

306 Remote port (JORPORT) Zoned (5, 0) The remote port of a the journal entries. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the remote port.
311 Remote address (JORADR) Char (46) The remote address of a the journal entries. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the remote address.

----

On Sat, Mar 29, 2025 at 10:40 AM Patrik Schindler<poc@xxxxxxxxxx> wrote:

Hello Robert,

Am 29.03.2025 um 14:05 schrieb Robert Rogerson<rogersonra@xxxxxxxxx>:

I'm pretty sure as the JOPGM in the journal is QZDASOINIT that the

setting of the order status to blank is not done by a program on the IBMi
but how do I prove or confirm this?

QZDASOINIT is the server job handling ODBC connections. These connections
are done over TCP/IP and may be initiated from outside the IBM i (clients),
or from inside (things running in PASE).

Does that help? If no, what additional information do you need?

I also agree with Daniel, that the update is most likely forced by the
.NET application over a direct ODBC-connection to the IBM i. Not sure if
this is how it should be or not.

:wq! PoC

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.