This section outlines some common problems that can arise when starting resources. It contains advice for dealing with the problems:
ServiceName - DLL initialization failure Initialization of the
dynamic link library c:\windows\system32\user32.dll failed.
The process is terminating abnormally.
http://msdn.microsoft.com
You lose the This Account, Password and Confirm Password entries when you make these changes, so make sure that you know those details before you click OK.
Select System Account as the Log On As option, and tick the box Allow Service to Interact with Desktop. This allows you to see any hidden dialog messages.
The BIP2228E message is logged by any broker that is started by a user who is not a member of the semaphore creator's primary group. The broker tries to access the semaphore, but fails with a permissions-related error. It then terminates with the BIP2228E message.
There are a number of potential problems that might arise when trying to start a broker on z/OS and these are described in the following sections.
verbx vsmdata,'noglobal,jobname(vcp0brk2)'where vcp0brk2 is the name of the failing job. Find 'VSM LOCAL DATA AREA AT ADDRESS '. The field ELIM gives the available region size, and must be greater than 0C800000. If the field SMFEL is not ffffffff, the IEFUSI exit has changed the allowable region size. This value must also be greater than 0C80000.
If you have an IEFUSI exit, check that the exit does not limit the broker address spaces. For example, a commonly-used field is OUCBSUBN. This can be STC or OMVS for the broker and indicates how the address space was started.
S STU3053 $HASP100 STU3053 ON STCINRDR IEF695I START STU3053 WITH JOBNAME STU3053 IS ASSIGNED TO USER STU3 , GROUP STCGROUP $HASP373 STU3053 STARTED +(broker53) 0 BIP9141W: The component was started. +(broker53) 0 BIP2001I: The WebSphere Business Integration Message Broker service has started process ID 33554919. +(broker53.default) 0 BIP2201I: Execution Group started: process '67109 442 196'; thread '0'; additional information 'broker53', '76eb7f2d-e800-00 00-0080-974c271866d2', 'default', 'true', 'Q4A3', 'false', 'ARG5D651', 'ARGO53', '********', 'false', 'f9c27f2d-e800-0000-0080-974c271866d2' , '/local/argo/driver/drv3', '/local/argo/tgrp53/broker53'. +(broker53.default) 0 BIP9137I: A work manager has been registered by R 443 RMS registration services, work manager name is BIP.STU30532.006710919 6.IBM.UA .
D OMVS,U=STU3 BPXO040I 18.49.59 DISPLAY OMVS 446 OMVS 000E ACTIVE OMVS=(68,05) USER JOBNAME ASID PID PPID STATE START CT_SECS STU3 STU30531 0069 33554696 33554919 HR 18.49.15 2.217 LATCHWAITPID= 0 CMD=bipbroker broker53 STU3 STU30532 03FD 67109196 67109222 HR 18.49.23 19.816 LATCHWAITPID= 0 CMD=DataFlowEngine broker53 76eb7f2d-e800-00 STU3 STU3053 0036 33554768 83886483 HRI 18.49.08 .653 LATCHWAITPID= 0 CMD=bipservice Q4A3BRK AUTO STU3 STU30532 03FD 67109222 33554696 1W 18.49.23 19.816 LATCHWAITPID= 0 CMD=bipimain DataFlowEngine broker53 76eb7f2 STU3 STU3053 0036 83886483 1 1WI 18.49.08 .653 LATCHWAITPID= 0 CMD=/local/argo/driver/drv3/bin/bipimain bip STU3 STU30531 0069 33554919 33554768 1W 18.49.15 2.217 LATCHWAITPID= 0 CMD=bipimain bipbroker broker53
The infrastructure main program bipimain is the first process in every address space. It starts either bipservice, bipbroker, DataFlowEngine, or bipuns as the second process in the same address space. For each execution group, an additional address space is started. In this example, only one execution group is available.
BIP8026W: Unable to start the component. The component could not be started using the service userid that was supplied when the component was created.This also happens with the User Name Server when you run that on Windows.
For example, if you specify NTSecurityDomainName on the -d flag on the mqsicreatebroker command as NYBROKER on local system \\NYBROKER, the service user ID on the -i flag on the mqsicreatebroker command cannot be nybroker.
You must delete your Configuration Manager (or User Name Server, or both) and re-create it using another user ID that has the correct authorizations.
mqsichangebroker brokername -i ServiceUserID -a ServicePassword -p DataSourcePasswordFor example, to change your logon password to user1pwd, your user id to user1, and your broker name to WBRK_BROKER, the command:
mqsichangebroker WBRK_BROKER -i user1 -a user1pwd -p user1pwd
mqsichangeconfigmgr -i ServiceUserID -a ServicePassword -p DataBasePasswordFor example, to change your logon password to user1pwd, your user id touser1, and your brokername to WBRK_BROKER, use the command:
mqsichangeconfigmgr -i user1 -a user1pwd -p user1pwd
Your components should now start.
IEA995I SYMPTOM DUMP OUTPUT 463 SYSTEM COMPLETION CODE=047 TIME=10.53.47 SEQ=00419 CPU=0000 ASID=008E PSW AT TIME OF ERROR 078D0000 98D09E52 ILC 2 INTC 6B ACTIVE LOAD MODULE ADDRESS=18D08828 OFFSET=0000162A NAME=SPECIALNAME 61819987 968995A2 A3618499 89A58599 */argoinst/driver* F1F46D82 96858261 A4A29961 93979761 *14_boeb/usr/lpp/* A6949889 61828995 61828997 89948189 *wmqi/bin/bipimai* 95 *n * DATA AT PSW 18D09E4C - 58109948 0A6B5820 B8E95020 GPR 0-3 00000000 0000003C 00000000 00000000 GPR 4-7 18D10300 18D115F0 00000013 00000004 GPR 8-11 18D111CF 18D101D0 18D0BBBE 18D0ABBF GPR 12-15 98D09BC0 18D101D0 98D09E22 00000000 END OF SYMPTOM DUMPwritten to the SDSF SYSLOG.
//MQP1BRK JOB 1,MSGCLASS=H //S1 EXEC PROC=MQP1BRKIf this works, the started task user ID is probably unable to access resources.
RDEFINE SURROGAT MQP1BRK.SUBMIT OWNER(mqp1BRK) AUDIT(ALL(READ)) PE MQP1BRK.SUBMIT CLASS(SURROGAT) ID(myid) ACC(READ)
This allows myid to put USER=MQ01BRK in the job card of a job and the job runs under the MQP1BRK user ID.
+(MA00BRK) 0 BIP2048E: An Exception was caught while issuing database SQL command connect. +(MA00BRK) 0 BIP2321E: Database error: ODBC return code '-1'. +(MA00BRK) 0 BIP2322E: Database error: SQL State '58004'; Native Error Code '-99999'
Batch job BIP$DB05 grants the necessary authorizations on the broker database tables, so this is unlikely to be the cause of the problem. The other authorizations must, however, be performed manually, for example using a SPUFI script.
SQLAllocConnect( hEnv=1, phDbc=&1c6bacec ) SQLAllocConnect( ) ---> SQL_ERROR SQLError( hEnv=1, hDbc=0, hStmt=0, pszSqlState=&19ca445c, pfNativeError=&19ca4458, pszErrorMsg=&1c3d9e50, cbErrorMsgMax=1024, pcbErrorMsg=&19ca4444 ) SQLError( pszSqlState="58004", pfNativeError=-99999, pszErrorMsg="{DB2 for OS/390}{ODBC Driver} SQLSTATE=58004 ERRLOC=2:170:6 RRS "CREATE THREAD" failed using DB2 system:DFL0 and Plan:DSNACLI RC=08 and REASON=00f30034", pcbErrorMsg=159) ---> SQL_SUCCESS SQLError( hEnv=1, hDbc=0, hStmt=0, pszSqlState=&19ca445c, pfNativeError=&19ca4458, pszErrorMsg=&1c3d9e50, cbErrorMsgMax=1024, pcbErrorMsg=&19ca4444 ) SQLError( pszSqlState="42505", pfNativeError=-922, pszErrorMsg="{DB2 for OS/390}{ODBC Driver} DSNT408I SQLCODE = -922, ERROR: AUTHORIZATION FAILURE: PLAN ACCESS ERROR. REASON 00F30034 DSNT418I SQLSTATE = 42505 SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNAET03 SQL PROCEDURE DETECTING ERROR ERRLOC=2:170:8", pcbErrorMsg=371 ) ---> SQL_SUCCESSIf the started task ID does not have SELECT authorization on tables SYSIBM.SYSSYNONYMS, SYSIBM.SYSDATABASE and SYSIBM.SYSTABLES, you see the following type of entry in the traceodbc file if ODBC tracing is turned on:
SQLTables( hStmt=1, szTableQualifier=Null Pointer, cbTableQualifier=0, szTableOwner="MA15USR", cbTableOwner=-3, szTableName=Null Pointer, cbTableName=0, szTableType=Null Pointer, cbTableType=0 ) SQLTables( ) ---> SQL_ERROR
(PMQ1BRK.default)[8]BIP2624E: Unable to connect to queue manager 'PMQ5': MQCC=2; MQRC=2025; message flow node 'ComIbmMQConnectionManager' (PMQ1BRK.default)[8]BIP2604E: Node failed to open WebsphereMQ queue 'INPUT1' owned by queue manager 'PMQ5': completion code 2; reason code 2025
ICH408I USER(TASKID1 ) GROUP(TSOUSER ) NAME(FRED (FRED) 959 /argo/MA11BRK/ENVFILE CL(DIRSRCH ) FID(01D7C7E2E3F0F8000F16000000000003) INSUFFICIENT AUTHORITY TO LOOKUP ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---) IEE132I START COMMAND DEVICE ALLOCATION ERROR IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=00A8. D J,BPXAS IEE115I 11.13.04 2001.212 ACTIVITY 601In this example, the started task ID did not have access to the HFS component. The ICH408I message shows:
You can use this information to correct the permissions and then reissue, in this example, the start broker request. This type of message is produced if the user issuing the command (which might be to start the broker, or to submit JCL to start one of the utility jobs) does not have the correct HFS permissions for the HFS component. Use the ICH408I information to rectify the problem.
Another possible reason for authorization failures is inconsistencies in the RACF definitions for a user ID in the MVS image and the OMVS segment. You should also check with your system administrator that the RACF ID used on MVS has a corresponding OMVS image created.
ICH408I USER(MA10USR ) GROUP(TSOUSER ) NAME(OTHER, A N (ANO) 484 /argo/MA10BRK/ENVFILE - --TIMINGS (MINS.)-- ----PAGING COUNTS--- -JOBNAME STEPNAME PROCSTEP RC EXCP CPU SRB CLOCK SERV PG PAGE SWAP VIO SWAPS CL(DIRSRCH ) FID(01D7D3E2E3F1F9002D08000000000003) INSUFFICIENT AUTHORITY TO LOOKUP ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---)
drwxrwx--- 5 BPXROOT ARGOUSR 8192 Jul 30 13:57 argoIssuing id MA00USR to find the group membership of started task ID MA00USR reveals:
uid=14938(MA00USR) gid=5(TSOUSER) groups=229(ARGOUSR)This means that the started task ID MA00USR potentially has rwx permissions on subdirectories to /argo because these are set for both the user and the group associated with MA00USR. If the permissions are not set correctly, you get the type of diagnostic shown in the scenario.
Related concepts
Broker
Broker domain
Related tasks
Starting and stopping a broker
Starting and stopping the Configuration Manager
Starting and stopping message flows
Checking APF attributes of bipimain on z/OS
Dealing with problems
Recovering after the Configuration Manager fails
MQ Java Client tracing
Related reference
mqsistart command
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16570_ |