ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
ZMSSTART - JVMJZBL1038E Child shell process exited with exit code: 8
Article ID: 238617
Updated On:
Products
COMMON SERVICES FOR Z/OS
Issue/Introduction
Running Common Services (CCS) 15.0...The ZMSSTART task will not start.
STC10747 ---- THURSDAY, 31 MAR 2022 ----
STC10747 IEF695I START ZMSSTART WITH JOBNAME ZMSSTART IS ASSIGNED TO USER ZMSADM
STC10747 $HASP373 ZMSSTART STARTED
STC10747 $HASP395 ZMSSTART ENDED - RC=0102
JVMJZBL2999T IS_INSTANCE_MOUNTED=$(df ${MSINST} | grep -c INSTANCE.CCSZFSB)
JVMJZBL2999T eval `echo '
JVMJZBL2999T if \0255 "${IS_INSTANCE_MOUNTED}" -eq 0 \0275; then
JVMJZBL2999T echo 'Instance zfs is not mounted.';
JVMJZBL2999T exit 8;
JVMJZBL2999T fi;
JVMJZBL2999T '`
JVMJZBL1005I Output from DD:STDENV config shell script:
JVMJZBL2999T Instance zfs is not mounted.
JVMJZBL2999T waiting for child shell process to complete
JVMJZBL2999T -> waitChild()
JVMJZBL1038E Child shell process exited with exit code: 8
JVMJZBL2999T <- waitChild()
JVMJZBL2999T <- adoptEnvironment()
JVMJZBL2999T <- run()
JVMJZBL2999T -> cleanup()
JVMJZBL2999I JZOS batch launcher elapsed time=0 seconds, cpu time=0.010000 seconds
JVMJZBL1042E JZOS batch launcher failed, return code=102
Cause
The deployment instance filesystem is not mounted or not named as expected.
Environment
Release : 15.0
Component : CCS MESSAGE SERVICE
Resolution
Review the Message Service deployment job (J2ZDPLOY) along with the input member J2ZSYM to verify name of filesystem used for deployment.
Hint: Look for value of DPLOYHLQ.
The default name for the instance zFS file for the Message Service server is &DPLOYHLQ..INSTANCE.CCSZFSB
Be sure filesystem is mounted
Feedback
Yes
No
Powered by
