Skip to Content
avatar image
Former Member

Operating System Collector - CPF1605 error

We have had the OS collector running now for a few years on both are development system and are production system. Recently however the log file for the OS collector on are development instance of SAP has been repeating the following error message every 3 minutes for the lat month.

LOG: Subsystem: R3_00 R3DEV400 Error CPF1605: in file /build/bas/640_REL/gen/optA/pfas41c2.c line 648

I know that CPF1605 is a Cannot allocate subsystem description error but both of are SAP instances show the same object lock on the R3_00 subsystem description by the system arbiter job QSYSARB4. The OS collector log file for are production however does not show this error. Both system's are running the same version of the OS V5R4M0 and both have the same PTF's applied to them. Any Idea's as to what the problem might be would be greatly appreciated.

Jason Duncan

SAP/iSeries Administrator

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 28, 2008 at 08:17 AM

    The code is executing API QWDRSBSD (Retrieve Subsystem Information) at the line that is mentioned in the message. The API needs an *EXCLRD lock on the subsystem description. The QSYSARB4 job usually has *SHRRD locks on all subsystem descriptions that belong to a started subsystem. According to the documentation, is should be possible to obtain an *EXCLRD lock on an object when another job has a *SHRRD lock.

    You can check if there are any locks stronger than *SHRRD on the subsystem description (WRKOBJLCK). Can you execute DSPSBSD for that subsystem from an interactive session?

    Kind regards,

    Christian Bartels.

    Add comment
    10|10000 characters needed characters exceeded