But my colleague said, that USR0330N delivers wrong user-IDs for the catalogued part. And he’s right. We’re using NAT 6.1.1.17 on Solaris and on Windows XP and on both environments, the catalog User-ID is wrong.
Can anyone reproduce this error? To make a quick test, just try out the SAG-delivered USR0330P for a Natural object with different user-IDs for the source and the catalogued file.
Sorry, but I am on mainframe. And the userexit is not marked as OS specific. So I think, the user exit must be the same :?:
This is what the doc reads:
Read Natural Object Directory NAT
.
Name of Interface ....... USR0330N /* Cataloged Interface
Name of Program ......... USR0330P /* Example for the Programmer
.
Function ................ Get directory information about a saved
and/or cataloged Natural object.
NOTE: For version NAT23 or above use
USR2018N
.
Keywords ................ DIRECTORY
and USR2018:
Read Natural Object Directory NAT
.
Name of Interface ....... USR2018N /* Cataloged Interface
Name of Program ......... USR2018P /* Example for the Programmer
.
Function ................ Get directory information about a saved
and/or cataloged Natural object.
.
Keywords ................ DIRECTORY
If you don’t have USR2018N, my SAG universe is destroyed
I just tried the running the sample provided for USR0330 on Windows using NAT6.1.1.19 and it seems to return the correct results. What was the “wrong” user-id being returned? Was it from a different object? or corrupt?
The next interesting thing is:
If I copy an Natural-Object from the mapped environment to my local environment via SPoD, all Properties are kept (Source User ID, Source date and Catalog date). The only exeption is the Catalog User ID.
Could it be, that the USR0330N-bug also causes this error?