Initiate thread returned error number EBUSY (3029)

I have a password validation/sync program (PWDVLD) on a v7r3 system that's called for exit point QIBM_QSY_VLD_PASSWRD exit point, format VLDP0100.

The program makes sure the new password is all uppercase (it's synchronizing with a v5r4 system that's at password level zero) and 10 characters or less (that's the validation part).

Then it uses RUNRMTCMD to run a program on the v5r4 system to change the password there. Any messages from RUNRMTCMD are sent back to the v7r3 system as a QSYSPRT spool file.

The PWDVLD program then declares a cursor, prepares it, and opens it for

 SELECT ORDINAL_POSITION, SPOOLED_DATA +
  FROM TABLE(SYSTOOLS/SPOOLED_FILE_DATA(+
         JOB_NAME =>''*''+
       , SPOOLED_FILE_NAME =>''QSYSPRT''))
 ORDER BY ORDINAL_POSITION+

Then it fetches the contents and displays them.

All that works most of the time.  For some users though, the first fetch gets the following errors:

 Cursor CS opened.
 Initiate thread returned error number EBUSY (3029)
 Job type: I, Job Subtype:  , Job Phase: Program
 Thread Enabled: No, Allow secondary threads: No
 Allow modification of secondary threads attribute: Yes
 Maximum number threads: 32768, Current number threads: 1
 Threads error;  reason code 0001.
 User-defined function error on member QSQPTABL.
 User-defined function error on member QSQPTABL.
 Trigger program or external routine detected an error.
 DSPLY  Fetch cs error. SQLSTATE=38501

I set up a test user for which I can reliably replicate this problem. The only thing different from another user that works is the test user has an expired password, so during signon it automatically went to the CHGPWD routine, which calls PWDVLD.

Any idea why this would cause the above errors?

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /