On Sat, 12 Jan 2019 14:59:05 +1100, Wayne Bickerdike wrote:
>Step end stats:
>
>IEF032I STEP/STEP020 /STOP 2019011.2148
>
> CPU: 0 HR 00 MIN 00.05 SEC SRB: 0 HR 00 MIN 00.01
>SEC
> VIRT: 7908K SYS: 260K EXT: 4K SYS: 10876K
>
> ATB- REAL: 3104K SLOTS: 0K
>
> VIRT- ALLOC: 12M SHRD: 0M
>
>
Look at module DFHEISUP in the load library. Is it marked RMODE(24)? According
to your Fault Analyzer report, the module is over 7 MB and it seems to be
loaded below the line. Your job is using only 4K above the line.
I would suggest you open a PMR with IBM.
--
Tom Marchant
>On Sat, Jan 12, 2019 at 2:52 PM Wayne Bickerdike <wayn...@gmail.com> wrote:
>
>> REGION=0M and same abend with REGION=512M.
>>
>> Took an SVC dump, here's some FA information.
>>
>> JOBNAME: $SDO512M SYSTEM ABEND: 106 S0W1 2019/01/11
>> 21:21:48
>>
>>
>> IBM Fault Analyzer Abend Job Information:
>>
>> Abend Date. . . . . . . . : 2019/01/11
>> Abend Time. . . . . . . . : 21:21:48
>> System Name . . . . . . . : S0W1
>> Job Type. . . . . . . . . : Batch
>> Job ID. . . . . . . . . . : JOB02430
>> Job Name. . . . . . . . . : $SDO512M
>> Job Step Name . . . . . . : n/a
>> ASID. . . . . . . . . . . : 1C
>> Abend TCB Address . . . . : 007FE990
>> Job Execution Class . . . : A
>> Region Size . . . . . . . : 0M
>> EXEC Program Name . . . . : DFHEISUP
>> User ID . . . . . . . . . : BDB204
>> Accounting Information. . : n/a
>>
>> Execution Environment:
>>
>> Operating System. . . . . : z/OS V2R2M0
>> Data Facility Product . . : DFSMS z/OS V2R2M0
>> CPU Model . . . . . . . . : 2817
>>
>> NOTE: The execution environment for this event is no longer valid, save
>> areas
>> and data might have subsequently been updated. This is normally
>> caused
>> by condition handling routine processing.
>>
>>
>>
>> Load Module Name. . . . . . : DFHEISUP
>>
>> At Address. . . . . . . . : 00007F90
>>
>> Load Module Length. . . . : X'7B6070'
>>
>>
>>
>> Machine Instruction . . . . : 0A08 SVC 8 (LOAD)
>>
>> At Address. . . . . . . . : 007BDD70 (Module DFHEISUP offset X'7B5DE0')
>>
>> AMODE . . . . . . . . . . : 31
>>
>>
>>
>> Additional instructions around event offset:
>>
>>
>>
>> Offset Hex Instruction
>>
>> -2C 58C0 0010 L R12,16
>>
>> -28 58C0 C000 L R12,0(,R12)
>>
>> -24 58C0 C004 L R12,4(,R12)
>>
>> -20 58C0 C144 L R12,324(,R12)
>>
>> -1C 58C0 C004 L R12,4(,R12)
>>
>> -18 BFCF C020 ICM R12,15,32(R12)
>>
>> -14 A784 0005 BRC 8,*+10
>>
>> -10 180C LR R0,R12
>>
>> -E A7F4 007D BRC 15,*+250
>>
>> -A 4120 7008 LA R2,8(,R7)
>>
>> -6 4100 2000 LA R0,0(,R2)
>>
>> -2 1B11 SR R1,R1
>>
>> 007BDD70 0A08 SVC 8 (LOAD)
>>
>> +2 58C0 322C L R12,556(,R3)
>>
>> +6 166C OR R6,R12
>>
>> +8 164C OR R4,R12
>>
>> +A A7F4 0071 BRC 15,*+226
>>
>> JOBNAME: $SDO512M SYSTEM ABEND: 106 S0W1 2019/01/11
>> 21:21:48
>> +2 58C0 322C L R12,556(,R3)
>>
>> +6 166C OR R6,R12
>>
>> +8 164C OR R4,R12
>>
>> +A A7F4 0071 BRC 15,*+226
>>
>> +E A7F8 0010 LHI R15,16
>>
>> +12 5820 7018 L R2,24(,R7)
>>
>> +16 1812 LR R1,R2
>>
>>
>>
>> Program Status Word (PSW) . : 078D0000 807BDD72
>>
>> PSW Summary . . . . . . . . : Primary Space Mode, PSW Key 8, AMODE 31,
>> Problem
>> State
>>
>>
>>
>> General Purpose Registers (AMODE: 64 31 24 , Bytes: Dec Hex ):
>>
>> R0: 007BDA48 (Module DFHEISUP + X'7B5AB8')
>>
>> R1: 00000000 (2,048 bytes of storage addressable)
>>
>> R2: 007BDA48 (Module DFHEISUP + X'7B5AB8')
>>
>> R3: 007BDC78 (Module DFHEISUP + X'7B5CE8')
>>
>> R4: 00000064 (1,948 bytes of storage addressable)
>>
>> R5: 00006FE8 (8,093,720 bytes of storage addressable)
>>
>> R6: 007BD800 (Module DFHEISUP + X'7B5870')
>>
>> R7: 807BDA40 (Module DFHEISUP + X'7B5AB0')
>>
>> R8: 007AED20 (Module DFHEISUP + X'7A6D90')
>>
>> R9: 007F8190 (32,368 bytes of storage addressable)
>>
>> R10: 00000000 (2,048 bytes of storage addressable)
>>
>> R11: 807BD82A (Module DFHEISUP + X'7B589A')
>>
>> R12: 00000000 (2,048 bytes of storage addressable)
>>
>> R13: 00006F50 (8,093,872 bytes of storage addressable)
>>
>> R14: 807BD8FE (Module DFHEISUP + X'7B596E')
>>
>> R15: 007BDC78 (Module DFHEISUP + X'7B5CE8')
>>
>> Abend Code. . . . . . . . . : S106-X'C'
>>
>> Machine Instruction . . . . : 0A0D SVC 13 (ABEND)
>> At Address. . . . . . . . : 01074DB8
>> AMODE . . . . . . . . . . : 31
>>
>> Instructions around point of failure:
>>
>> Offset Hex Instruction
>> -22 43C0 5078 IC R12,120(,R5)
>> -1E 185C LR R5,R12
>> -1C 8950 0008 SLL R5,8
>> -18 16F5 OR R15,R5
>> -16 1824 LR R2,R4
>> -14 1837 LR R3,R7
>> -12 184B LR R4,R11
>> -10 18E1 LR R14,R1
>> -E 89E0 000C SLL R14,12
>> -A 54E0 9038 N R14,56(,R9)
>> -6 A5EA 8400 OILH R14,X'8400'
>> -2 181E LR R1,R14
>> 01074DB8 0A0D SVC 13 (ABEND)
>> +2 18FB LR R15,R11
>> +4 180C LR R0,R12
>> +6 181D LR R1,R13
>> +8 58E0 02FC L R14,764
>> +C 58D0 E248 L R13,584(,R14)
>>
>> +10 0DED BASR R14,R13
>>
>> +12 18BF LR R11,R15
>>
>>
>>
>> Program Status Word (PSW) . : 070C1000 81074DBA
>>
>> PSW Summary . . . . . . . . : Primary Space Mode, PSW Key 0, AMODE 31,
>>
>> Supervisor State
>>
>>
>>
>> General Purpose Registers (AMODE: 64 31 24 , Bytes: Dec Hex ):
>>
>> R0: 0_00001F00 (Storage invalid)
>>
>> R1: 0_84106000 (Module IGC0013{ + X'9E000')
>>
>> R2: 0_26080021 (Storage invalid)
>>
>> R3: 0_0000000C (2,036 bytes of storage addressable)
>>
>> R4: 0_00000014 (2,028 bytes of storage addressable)
>>
>> R5: 0_007FF8F0 (1,808 bytes of storage addressable)
>>
>> R6: 0_7F5F7100 (1,089,280 bytes of storage addressable)
>>
>> R7: 0_0000000C (2,036 bytes of storage addressable)
>>
>> R8: 0_7F5F7168 (1,089,176 bytes of storage addressable)
>>
>> R9: 0_010752E0 (7,456 bytes of storage addressable)
>>
>> R10: 0_00000024 (2,012 bytes of storage addressable)
>>
>> R11: 0_00000014 (2,028 bytes of storage addressable)
>>
>> R12: 0_00000000 (2,048 bytes of storage addressable)
>>
>> R13: 0_7F5F7168 (1,089,176 bytes of storage addressable)
>>
>> R14: 0_84106000 (Module IGC0013{ + X'9E000')
>>
>> R15: 0_0000000C (2,036 bytes of storage addressable)
>>
>>
>>
>> Load Module Name. . . . . . : IGC0101C (In Link Pack Area)
>>
>> At Address. . . . . . . . : 0417D000
>>
>> Load Module Length. . . . : X'1D6F0'
>>
>>
>>
>> Machine Instruction . . . . : n/a
>>
>> At Address. . . . . . . . : 0418FDF0 (Module IGC0101C offset X'12DF0')
>>
>> AMODE . . . . . . . . . . : 31
>>
>>
>>
>> Additional instructions around event offset:
>>
>>
>>
>> Offset Hex Instruction
>>
>> No instructions available.
>>
>>
>>
>>
>>
>> Program Status Word (PSW) . : 070C1000 8418FDF2
>>
>> PSW Summary . . . . . . . . : Primary Space Mode, PSW Key 0, AMODE 31,
>>
>> Supervisor State
>>
>>
>>
>> General Purpose Registers (AMODE: 64 31 24 , Bytes: Dec Hex ):
>>
>> R0: 0032D125 (Module DFHEISUP + X'325195')
>>
>> R1: 7F5F7DF0 (1,085,968 bytes of storage addressable)
>>
>> R2: 0418FE08 (Module IGC0101C + X'12E08' - storage invalid)
>>
>> R3: 00000000 (2,048 bytes of storage addressable)
>>
>> R4: 007C5F68 (237,720 bytes of storage addressable)
>>
>> R5: 7F5F7428 (1,088,472 bytes of storage addressable)
>>
>> R6: 04192530 (Module IGC0101C + X'15530' - storage invalid)
>>
>> R7: 7F5F7CF0 (1,086,224 bytes of storage addressable)
>> R8: 7F5F7438 (1,088,456 bytes of storage addressable)
>> R9: 007FC2E4 (15,644 bytes of storage addressable)
>> R10: 007FC258 (15,784 bytes of storage addressable)
>> R11: 00000000 (2,048 bytes of storage addressable)
>> R12: 7F5F7078 (1,089,416 bytes of storage addressable)
>> R13: 7F5F7078 (1,089,416 bytes of storage addressable)
>> R14: 8418FDE0 (Module IGC0101C + X'12DE0' - storage invalid)
>> R15: 00000000 (2,048 bytes of storage addressable)
>>
>>
>>
>>
>> On Thu, Jan 10, 2019 at 5:56 AM Mike Schwab <mike.a.sch...@gmail.com>
>> wrote:
>>
>>> Fetch usually fails with INSUFFICIENT MEMORY. Increase region size.
>>> If you don't have one, look at the memory stats at the end of step
>>> messages to see what was used and double. Otherwise suggest REGION=4M,
>>> 5M, 6M, 7M, 20M, 32M, 64M, etc.
>>>
>>> On Wed, Jan 9, 2019 at 12:26 PM Peter Relson <rel...@us.ibm.com> wrote:
>>> >
>>> > I don't think the abend 106 that is discussed is part of the original
>>> > discussion, so I guessed that it could do with a different thread name.
>>> >
>>> > The abend 106 itself is not helpful in finding out what is going on
>>> > because that is just the generic result of a preceding problem which
>>> > likely had message(s) and/or abend(s).
>>> >
>>> > It appears that what Wayne posted was truncated.
>>> >
>>> > IEW4000I FETCH FOR MODULE CEEBINIT FROM DDNAME *VLF* FAILED BECAUSE
>>> > INSUFFICI
>>> > CSV031I LIBRARY ACCESS FAILED FOR MODULE CEEBINIT, RETURN CODE 24,
>>> REASON
>>> > CODE 2
>>> >
>>> > Can we get the complete information? It probably doesn't matter much.
>>> The
>>> > missing part of IEW4000I is not going to help, but possibly having the
>>> > rest of CSV031I (including the complete reason code) would.
>>> >
>>> > In at least one case, Fetch processing did a getmain, and the getmain
>>> > failed. Why? Because the application needed more region than was
>>> defined,
>>> > probably.
>>> > I'd suggest capturing a dump on the IEW4000I message issued by nucleus
>>> > module CSVLLTCH. That's what IBM service will likely ask for.
>>> >
>>> > The message can also occur because of a problem with doing the
>>> relocation
>>> > processing (I'm not sure why that lands with a message about
>>> insufficient
>>> > storage).
>>> >
>>> > Peter Relson
>>> > z/OS Core Technology Design
>>> >
>>> >
>>> > ----------------------------------------------------------------------
>>> > For IBM-MAIN subscribe / signoff / archive access instructions,
>>> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>>
>>>
>>> --
>>> Mike A Schwab, Springfield IL USA
>>> Where do Forest Rangers go to get away from it all?
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>
>>
>> --
>> Wayne V. Bickerdike
>>
>>
>
>--
>Wayne V. Bickerdike
>
>----------------------------------------------------------------------
>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
