ODBC data source not showing fields after OS upgrade

Are you getting an error?  When you or the UPS jobs connects, it will be assigned to a QZDASOINIT (QZDASSINIT if you use SSL) job.  That job log will generally have any errors in in.

One way to find the right QZDASOINIT job is to establish a connection, try something that fails, and them log onto a green screen and do a

WRKOBJLCK yourprofilename *USRPRF

Where yourprofilename is the name of your IBM i user profile (or the profile UPS uses).

That's because when a job logs on, it automatically grabs a shared read lock on the user profile associated with the job.

So once you find the QZDASOINIT job, display the job log, press F10 to see detailed messages, look for error messages, and if you find any, put your cursor on each one in sequence and hit F1 to display the full message detail.

Post the full message detail (sometimes it runs to a couple of pages) for each message you find that looks like it might be related to the problem.  Sometimes the message will provide recover actions.  Try those and post any positive or negative results.

Thanks Gary.   I ended up having to call IBM and we believe that we tracked it down to DB cross reference files.   I am going to run a RCLSTG tonight and see if that helps.   I am going to take a look at those job logs also.

Thanks!

Hi Tom,

Yes, we ran the RCLDBXREF prior to coming to the conclusion to run the RCLSTG.   This is a small quick system.  I ran the *DBXRF after hours and it literally took about a minute.    

Thanks to both of you.

Jon