Re: Initiate thread returned error number EBUSY (3029)

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Rob,

Just posting this followup for the archives.  I took your advice 
(thanks!) and opened a case, and IBM noted that my customer is behind on 
PTFs.  Once they got up to date, the problem went away.

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

On 12/9/2020 5:48 AM, Rob Berendt wrote:
> SELECT
>    MESSAGE_FILE_LIBRARY,               -- MSGF_LIB    VARCHAR(10)
>    MESSAGE_FILE,                       -- MSGF        VARCHAR(10)
>    MESSAGE_ID,                         -- MSGID       CHARACTER(7)
>    MESSAGE_TEXT,                       -- MSG_TEXT    VARGRAPHIC(132)
>    MESSAGE_SECOND_LEVEL_TEXT,          -- SECLVL      VARGRAPHIC(3000)
> ...
> FROM QSYS2.MESSAGE_FILE_DATA
> WHERE MESSAGE_TEXT LIKE 'Threads error%';
>
> Based on it being easily reproducible, and the fact that the above sql says you are getting QSYS/QCPFMSG/CPFB925, and the second level text ends with 'If the problem persists, call service.' I might open a case.  Perhaps there's something wrong with the underlying program associated with the service you are using in which it cannot handle this particular situation.
>
> The alternative might be to not send the spool file over from the V5R4 system but convert that to an alternative file, send that over, and read that instead.
>
> Rob Berendt