One more thing for those following this thread; For now, I coded the following 
to produce the report:

//SPECIAL   DD  *                        
EXCLUDE CPC=1234-56789,IMAGE_ID=SNDBOX,  
 START=2019/02/01/23,RESUME=2019/03/02/01

When I know I will be producing 70s and 89s for that lpar again, I'll remove 
those three lines.

Bob

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Friday, February 08, 2019 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JVM errors running daily SCRT at currently available V26.1

Roger,

I misspoke! Your clue made me take a another look at all the messages, user 
guide in hand.

We have a sandbox lpar that is normally up and active. It has been down 
recently and I just noticed the SCRTTOOL053 message in the output. The code, in 
part, states the following:

SCRTTOOL053 type-serial: NO SMF nn RECORDS FOUND FOR LPAR lparname

Explanation: The input stream for the SCRT contains more than one SMF type 89 
record for LPAR lparname and
zero SMF type 70 subtype 1 records for LPAR lparname OR the input stream 
contains more than one SMF type 70
subtype 1 record for LPAR lparname and zero SMF type 89 records for LPAR 
lparname. The SCRT issues a return code
of 16. No sub-capacity report is produced.

Thanks for the heads-up! No sure why I missed it the first few times I looked 
at today’s SYSOUT. And thanks to Jerry, Mike and Kayhan for their suggestions.

Bob


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Roger Lowe
Sent: Friday, February 08, 2019 8:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JVM errors running daily SCRT at currently available V26.1

On Fri, 8 Feb 2019 11:20:36 +0000, Richards, Robert B. 
<robert.richa...@opm.gov> wrote:

>Has anyone else seen this recently? It worked yesterday, failed today and to 
>the best of my knowledge, nothing has been changed (production lpar at z/OS 
>2.2).
>
>JVMJZBL1001N JZOS batch Launcher Version: 2.4.8 2017-09-13
>JVMJZBL1002N (C) Copyright IBM Corp. 2005, 2016
>java version "1.8.0_171"
>Java(TM) SE Runtime Environment (build 8.0.5.15 - 
>pmz6480sr5fp15-20180502_01(SR5 FP15))
>IBM J9 VM (build 2.9, JRE 1.8.0 z/OS s390x-64 Compressed References 
>20180425_385365 (JIT enabled, AOT enabled)
>OpenJ9   - a7ffbfe
>OMR      - a531219
>IBM      - 59ef3dc)
>JVMJZBL1015N MVS commands are DISABLED
>JVMJZBL1023N Invoking com.ibm.scrt.SCRTe.main()...
>JVMJZBL1043N The Java virtual machine completed with System.exit(16)
>

Do you have any SCRT* prefixed messages AFTER the JVMJZBL1043N message? I have 
had a previous System.exit(8) issue which had a bunch of SCRT* prefixed 
messages associated with it

Roger

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to