byimw02
0 pts. | Apr 15 2005 9:53AM GMT
I concur with Jonathan. What is the specific problem? Whatever you are trying to accomplish, remember all initiated jobs require a user profile. Where the user profile is retrieved is dependent on how the job is initiated. The profile can be explicitly provided using the various submit commands and signon screens/panels or implicitly in job descriptions and device descriptions. A batch job will have the user profile assigned to it at submission. All job scheduler packages allow the option to assigned it explicitly in a command parameter or implicitly from a job description. The user id in the PDS will be the user assigned at the job’s submission. Hope this helps. Ciao.
Dipendra
0 pts. | Apr 15 2005 10:41AM GMT
Hi,
Actually one file has some records with User value ‘QUS’.Other records contains the user id of the user who updated the record using interactive menus. The client has asked me to find from where these records with user id ‘QUS’ is comming. Since QUS user profile does not exist on the system, I suppose this must be done from a job running under system user profile QUSER whose first 3 char( user field in the file have length 3)is QUS.
Can you suggest a reason/way to track the job/pgm doing this.
Thanks & Regards
Dipendra
byimw02
0 pts. | Apr 18 2005 9:19AM GMT
The QUSER profile exists on all iSeries systems as part of the basic OS install. It is possible someone at the user installation delete it (not recommended) or you do not have the proper authority to view the Q* profiles. I am not sure what the user id info has QUS? Someone could have created a profile named QUS. First of all, I would look up all programs that update this PF and examine how the programs are referenced, e.g., via menu, explicit call from command line. Also check if file can be updated via DBU, DFU or other file utility which bypass all pre-set error and logging functions. With a file utility, someone can enter a non-existent profile id into the field along with other questionable data. Hope this helps.
TomLiotta
7670 pts. | Jun 3 2005 12:09AM GMT
To general possibilities seem to make sense:
1) Journal the file through database journaling, perhaps only for *AFTER images and onitting *OPNCLO. The journal entry will record everything that’s appropriate.
2) Turn on object auditing for the file object. The system security audit journal can then track accesses of the file object and again record the needed info.
I haven’t seen only the first three characters before, but I have seen where the servers report userid as a null-terminated string. We’ve submitted problem reports to IBM and gotten PTFs created. This _could_ be a similar situation.






