ok – several ways to do this – depending on our requirements
for example you can change user at the remote end to work as the logged on user, you can adopt authority to permit the intersystem access, while still working as the original user id, or (normally easiest) stamp the name of the user making the transaction to an audit file, this can be written directly from the calling program
Discuss This Question: 1  Reply