It's late, so I don't have tons of information at my fingertips, but let me try to explain as best as I can recall. When you create a connection using the toolbox, the toolbox launches a job named QZRCSRVS (by default these jobs run in QUSRWRK). Typically in a situation like this when a ProgramCall hangs, it's because the program called halted with a message. If that's the case here, you'll see the message in the QSYSOPR message queue as well as in the job's joblog. Still can't find the right job? You can also programmatically determine which QZRCSRVS job is the one you want. If you take a look at the AS400 class, there is a method called getJobs which returns an array of jobs. Now, different jobs are started for different services, such as signon and database. If you pass it the right parameter (I believe it's COMMANDCALL), you'll get an array of jobs used for program and command calls. Now, I can't think of a situation where there is more than one job, so my guess is that if you dump the attribute of the first entry in the returned array (I think the methods getName, getUser and getNumber will work) and dump that with your "Program about to be called" message. Then look at the resulting job to see what the hangup is. Joe > From: John Gilmore-Baldwin > > About to connect > Got connected > About to call program
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.