Abend B37-04 [1 Attachment]

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Abend B37-04 [1 Attachment]

Hercules390 - Mvs mailing list
Okay, the following APPEARED to *mostly* work.

(By "mostly" I mean it DID start and it DID appear to read my tape.)


    //FISHGENR JOB  1,FISH,MSGCLASS=X,NOTIFY=&SYSUID
    //         EXEC PGM=IEBGENER
    //SYSIN    DD   DUMMY
    //SYSPRINT DD   SYSOUT=*
    //SYSUT1   DD   UNIT=591,LABEL=(,BLP),
    //         DSN=Q.FISHTEST.AWS,VOL=SER=DUMMY,
    //         DISP=(OLD,KEEP,KEEP),
    //         DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720)
    //SYSUT2   DD   UNIT=A99,VOL=SER=FISH01,
    //         DSN=IBMUSER.FISH.TESTFILE.#001,
    //         SPACE=(CYL,(1000,100)),
    //         DISP=(NEW,KEEP,DELETE),
    //         DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)
    //


The tape stayed loaded, and "MVS" displayed:

    09.17.21 JOB00280 *01 IEF238D FISHGENR - REPLY DEVICE NAME OR 'CANCEL'.


So I replied "r 1,591" (the drive my tape was loaded on):

    09.19.16           r 1,591
    09.19.16 JOB00280  IEE600I REPLY TO 01 IS;591


The tape then UNLOADED(!), and "MVS" then displayed:

    09.19.16 JOB00280  IEF503I UNIT 0591 INCORRECT VOLUME LABEL


and Hercules displayed:

    HHC00224I 0:0591 Tape file *, type aws: display "D       " / "MDUMMY N" (alternating)


So I "devinit"ed the drive in Hercules to mount the SAME FREAKING TAPE THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does "MVS" insist on purposely unloading the damn tape I told it to use?!  What is UP with that?!), and, miracles of miracles, the job took off running!  (Yea!)

But the celebration was short lived unfortunately.  :(

    09.19.16 JOB00280  IEF234E D 0591
    09.19.16 JOB00280 *IEF233A M 0591,DUMMY ,,FISHGENR,,Q.FISHTEST.AWS
    09.20.10 JOB00280  IEC030I B37-04,IFG0554A,FISHGENR,,SYSUT2,0A99,FISH01,
     IBMUSER.FISH.TESTFILE.#001
    09.20.10 JOB00280  IEF234E K 0591,DUMMY ,PVT,FISHGENR
    09.20.10 JOB00280  IEF404I FISHGENR - ENDED - TIME=09.20.10


The printout is attached.

I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37 REASON CODE=00000004" means, but in the meantime if there's anyone that could provide to this inexperienced newbie any insight on the matter, I'd be *very* grateful.

Thanks.

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list


On Wed, Jan 25, 2017 at 07:56:49AM -0800, ''Fish' (David B. Trout)' [hidden email] [H390-MVS] wrote:
 
> I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37
> REASON CODE=00000004" means, but in the meantime if there's anyone that
> could provide to this inexperienced newbie any insight on the matter, I'd
> be *very* grateful.
 
QuickRef to the rescue.  This is from a z/OS system, but should still be
applicable:

Return Code Explanation

04        During end-of-volume processing, one of the following occurred:

          1.  For an output data set, all space was used on the current
              volume and no more volumes were specified.

          2.  The system had to demount a volume in order to mount the
              next volume of the data set. It was unable to demount the
              volume for one of the following reasons:

              a.  The volume was permanently resident
              b.  The volume was reserved
              c.  Another job had data sets allocated on the volume
              d.  There were open data sets on the volume for the failing
                  task.

          For an output data set on a direct access device, the system
          might have needed to demount the volume for one of the following
          reasons:

            o   No more space was available on the volume.

            o   The data set already had 16 extents, but required more
                space.

            o   The data set has reached the 65535 tracks per volume limit.

            o   More space was required, but the volume table of contents
                (VTOC) was full.  If additional space were allocated,
                another data set control block (DSCB) might have been
                needed, but could not have been written.

            For an output data set on magnetic tape, a volume needed to be
            demounted because the reflective spot was encountered and more
            records were to be written.

            For an input data set on more than one volume, one of the
            volumes needed to be demounted so that the next one could be
            mounted, but the system was unable to demount the volume.


P.S.  I'm at work at the moment.  The z/OS system in question is running in
real iron, not under Hercules.  No licenses were harmed in the composition
of this e-mail.  :-)



--

Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
On 2017-01-26 2:56 AM, ''Fish' (David B. Trout)' [hidden email]
[H390-MVS] wrote:
> So I "devinit"ed the drive in Hercules to mount the SAME FREAKING TAPE
> THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does "MVS" insist on
> purposely unloading the damn tape I told it to use?! What is UP with
> that?!)
As mentioned previously, unless the magnetic label matches the volume
serial requested by the job, any pre-mounted volumes are unloaded to
ensure that the incorrect volume does not get processed.  Such
recognition can be done for SL or AL, but not for NL or BLP.

Re the SB37 abend, as Kevin says, you ran out of space on the output
disk file - so that is not a tape processing problem.

Cheers,
Greg



------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/H390-MVS/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/H390-MVS/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
B37-04 is out of space and no more extents.

Joe

On Wed, Jan 25, 2017 at 9:56 AM, ''Fish' (David B. Trout)'
[hidden email] [H390-MVS] <[hidden email]> wrote:

>
> [Attachment(s) <#m_-5165990588309151671_TopText> from "Fish" (David B.
> Trout) included below]
>
> Okay, the following APPEARED to *mostly* work.
>
> (By "mostly" I mean it DID start and it DID appear to read my tape.)
>
> //FISHGENR JOB 1,FISH,MSGCLASS=X,NOTIFY=&SYSUID
> // EXEC PGM=IEBGENER
> //SYSIN DD DUMMY
> //SYSPRINT DD SYSOUT=*
> //SYSUT1 DD UNIT=591,LABEL=(,BLP),
> // DSN=Q.FISHTEST.AWS,VOL=SER=DUMMY,
> // DISP=(OLD,KEEP,KEEP),
> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720)
> //SYSUT2 DD UNIT=A99,VOL=SER=FISH01,
> // DSN=IBMUSER.FISH.TESTFILE.#001,
> // SPACE=(CYL,(1000,100)),
> // DISP=(NEW,KEEP,DELETE),
> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)
> //
>
> The tape stayed loaded, and "MVS" displayed:
>
> 09.17.21 JOB00280 *01 IEF238D FISHGENR - REPLY DEVICE NAME OR 'CANCEL'.
>
> So I replied "r 1,591" (the drive my tape was loaded on):
>
> 09.19.16 r 1,591
> 09.19.16 JOB00280 IEE600I REPLY TO 01 IS;591
>
> The tape then UNLOADED(!), and "MVS" then displayed:
>
> 09.19.16 JOB00280 IEF503I UNIT 0591 INCORRECT VOLUME LABEL
>
> and Hercules displayed:
>
> HHC00224I 0:0591 Tape file *, type aws: display "D " / "MDUMMY N"
> (alternating)
>
> So I "devinit"ed the drive in Hercules to mount the SAME FREAKING TAPE
> THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does "MVS" insist on purposely
> unloading the damn tape I told it to use?! What is UP with that?!), and,
> miracles of miracles, the job took off running! (Yea!)
>
> But the celebration was short lived unfortunately. :(
>
> 09.19.16 JOB00280 IEF234E D 0591
> 09.19.16 JOB00280 *IEF233A M 0591,DUMMY ,,FISHGENR,,Q.FISHTEST.AWS
> 09.20.10 JOB00280 IEC030I B37-04,IFG0554A,FISHGENR,,SYSUT2,0A99,FISH01,
> IBMUSER.FISH.TESTFILE.#001
> 09.20.10 JOB00280 IEF234E K 0591,DUMMY ,PVT,FISHGENR
> 09.20.10 JOB00280 IEF404I FISHGENR - ENDED - TIME=09.20.10
>
> The printout is attached.
>
> I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37
> REASON CODE=00000004" means, but in the meantime if there's anyone that
> could provide to this inexperienced newbie any insight on the matter, I'd
> be *very* grateful.
>
> Thanks.
>
> --
> "Fish" (David B. Trout)
> Software Development Laboratories
> http://www.softdevlabs.com
> mail: [hidden email]
>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
On 1/25/2017 10:56 AM, ''Fish' (David B. Trout)' [hidden email]
[H390-MVS] wrote:
>     //         DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)

If you're going to a 3390 (or 3380), then 30720 will write one block per
track. If you used 27648 you get two blocks per track on a 3390; 15360
on a 3380 for three blocks. (If you rerun your job, don't forget to
delete the bad data set [use IDCAMS DELETE dsn or RFE or whatever yoiur
editor is]).

FYI, the CBT tape/disks have several versions of a TSO BLKnnnn program
that allows calculation of optimal block sizes by device type.

When I use large data sets, I have a work pack that's completely empty,
allowing me to allocate the entire pack. I use
SPACE=(CYL,(nnnn,nnnn),RLSE) - the release parameter frees unused space
at the end of step, and gives you an idea how much space you really need
- you can do another IEBGENER to the intended permanent disk pack.

Gerhard Postpischil
Bradford, VT
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
 - - - In [hidden email], <david.b.trout@...> wrote:
> Okay, the following APPEARED to *mostly* work. > (By "mostly" I mean it DID start and it DID appear to read my tape.)
 > //FISHGENR JOB 1,FISH,MSGCLASS=X,NOTIFY=&SYSUID
> // EXEC PGM=IEBGENER
> //SYSIN DD DUMMY
> //SYSPRINT DD SYSOUT=*
> //SYSUT1 DD UNIT=591,LABEL=(,BLP),
> // DSN=Q.FISHTEST.AWS,VOL=SER=DUMMY,
> // DISP=(OLD,KEEP,KEEP),
> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720)
> //SYSUT2 DD UNIT=A99,VOL=SER=FISH01,
 

 That hard-coded a specific UNIT and VOL=SER in away
 that only allows one output disk volume.
 

 That is fine but it might be better to relax to something like:
 

 //SYSUT2 DD UNIT=(33?0,3),
 
> // DSN=IBMUSER.FISH.TESTFILE.#001,
> // SPACE=(CYL,(1000,100)),
 

 

 MVS will allocate exactly 1000 cylinders in one to five extents
 and then add 100 cylinders in one to five extents until either
 the hard-coded single disk volume is full or there are sixteen
 extents.  MVS 3.8j does not support disks well that have more
 than 4369 cylinders so I won't mention the 65536 number of
 tracks per data set per volume restriction.
 

 That would not use all of the space on any disk type that
 I know of.
 

 Are you using:
 3390-1
 3380-2
 9345-2 ( best but the last I saw, not supported )
 

 Note, if you tried something like 3390-2 or 3390-3, the
 operating system does not take secondary extents properly.
 i.e. You get your primary allocation if one extent is available
 but that is all that she wrote.

 

 Suggest that you code:

 

 // SPACE=CYL,(the-maximum-number-of-cylinders,the-maximum-number-of-cylinders),RLSE),

 

 

 3380-1   885 minus track zero and VTOC cylinders.
 3380-2   1770 minus track zero and VTOC cylinders.
 3390-1   1113  minus track zero and VTOC cylinders.

 3390-2184  2184 minus track zero and VTOC cylinders.

 
> // DISP=(NEW,KEEP,DELETE),
 

 I'm opinionated but if using a "normal" HERC01. type
 of data set would prefer:
 

 // DISP=(NEW,CATLG,DELETE),

 

 > // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)
 

 A really bad BLKSIZE for 3380 and 3390.
 Would be okay for a 3375 but not optimum..
 The poor BLKSIZE wastes too much space on a track.
 Try:
 

 For any 3380, BLKSIZE=15360
 For any 3390, BLKSIZE=27648
 
> //
 
 > The tape stayed loaded, and "MVS" displayed:
 > 09.17.21 JOB00280 *01 IEF238D FISHGENR - REPLY DEVICE NAME OR 'CANCEL'.
 > So I replied "r 1,591" (the drive my tape was loaded on):
 > 09.19.16 r 1,591
> 09.19.16 JOB00280 IEE600I REPLY TO 01 IS;591
 
That caused MVS to vary 591 online and re-try allocation.
 Since the JCL specified 591, that is what it found.

 > The tape then UNLOADED(!), and "MVS" then displayed:
 > 09.19.16 JOB00280 IEF503I UNIT 0591 INCORRECT VOLUME LABEL
 > and Hercules displayed:
 > HHC00224I 0:0591 Tape file *, type aws: display "D " / "MDUMMY N" (alternating)
 
 Good.
 

 MVS found an unknown and unlabeled tape on a tape
 drive so got rid of it.

> So I "devinit"ed the drive in Hercules to mount the SAME FREAKING
 >TAPE THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does
 >"MVS" insist on purposely unloading the damn tape I told it to use?!
 >What is UP with that?!), and, miracles of miracles, the job took off
 >running! (Yea!)
 

 MVS got rid of the unlabelled and unknown tape, then said to
 devinit the tape, then accepted what you then devinited.
 Did you expect MVS to accept a random unknown and
 unlabeled tape?  You have the wrong operating system for that.
 
> But the celebration was short lived unfortunately. :(
 > 09.19.16 JOB00280 IEF234E D 0591
> 09.19.16 JOB00280 *IEF233A M 0591,DUMMY ,,FISHGENR,,Q.FISHTEST.AWS
> 09.20.10 JOB00280 IEC030I B37-04,IFG0554A,FISHGENR,,SYSUT2,0A99,FISH01,
> IBMUSER.FISH.TESTFILE.#001
> 09.20.10 JOB00280 IEF234E K 0591,DUMMY ,PVT,FISHGENR
> 09.20.10 JOB00280 IEF404I FISHGENR - ENDED - TIME=09.20.10
 > The printout is attached.
 
SB37-04 says it all.
 You did not allocate enough space with a reasonable BLKSIZE to
 hold the tape's contents.
 

 How many bytes would the tape image be if uncompressed.
There is a nifty utility AWSBrowse that could check quickly.
That would give a hint as to how much MVS disk space that
 you will need to hold.

> I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37
 > REASON CODE=00000004" means, but in the meantime if there's anyone
 >that could provide to this inexperienced newbie any insight on the matter,
 >I'd be *very* grateful.
 > Thanks.
 > --
> "Fish" (David B. Trout)
> Software Development Laboratories
 > http://www.softdevlabs.com http://www.softdevlabs.com
> mail: fish@... mailto:fish@...
 

 It's a common issue so many can and will help.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
Change the block size to 27648. This allows 2 blocks on each track of 27 1024 byte records. Your block size of 30720 only allows 1 block per track wasting the rest of the space. Also for normal datasets the largest they can be is 64K tracks which comes out to 4369 cylinders. Later versions of MVS aka z/OS support  dd parm of DSNTYPE=LARGE but the program writing the data set has to be updated to recognize it. Don't know if iebgener was updated.

Laddie Hanus

Sent from whatever device I am using.

> On Jan 25, 2017, at 8:56 AM, ''Fish' (David B. Trout)' [hidden email] [H390-MVS] <[hidden email]> wrote:
>
> [Attachment(s) from "Fish" (David B. Trout) included below]
> Okay, the following APPEARED to *mostly* work.
>
> (By "mostly" I mean it DID start and it DID appear to read my tape.)
>
> //FISHGENR JOB 1,FISH,MSGCLASS=X,NOTIFY=&SYSUID
> // EXEC PGM=IEBGENER
> //SYSIN DD DUMMY
> //SYSPRINT DD SYSOUT=*
> //SYSUT1 DD UNIT=591,LABEL=(,BLP),
> // DSN=Q.FISHTEST.AWS,VOL=SER=DUMMY,
> // DISP=(OLD,KEEP,KEEP),
> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720)
> //SYSUT2 DD UNIT=A99,VOL=SER=FISH01,
> // DSN=IBMUSER.FISH.TESTFILE.#001,
> // SPACE=(CYL,(1000,100)),
> // DISP=(NEW,KEEP,DELETE),
> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)
> //
>
> The tape stayed loaded, and "MVS" displayed:
>
> 09.17.21 JOB00280 *01 IEF238D FISHGENR - REPLY DEVICE NAME OR 'CANCEL'.
>
> So I replied "r 1,591" (the drive my tape was loaded on):
>
> 09.19.16 r 1,591
> 09.19.16 JOB00280 IEE600I REPLY TO 01 IS;591
>
> The tape then UNLOADED(!), and "MVS" then displayed:
>
> 09.19.16 JOB00280 IEF503I UNIT 0591 INCORRECT VOLUME LABEL
>
> and Hercules displayed:
>
> HHC00224I 0:0591 Tape file *, type aws: display "D " / "MDUMMY N" (alternating)
>
> So I "devinit"ed the drive in Hercules to mount the SAME FREAKING TAPE THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does "MVS" insist on purposely unloading the damn tape I told it to use?! What is UP with that?!), and, miracles of miracles, the job took off running! (Yea!)
>
> But the celebration was short lived unfortunately. :(
>
> 09.19.16 JOB00280 IEF234E D 0591
> 09.19.16 JOB00280 *IEF233A M 0591,DUMMY ,,FISHGENR,,Q.FISHTEST.AWS
> 09.20.10 JOB00280 IEC030I B37-04,IFG0554A,FISHGENR,,SYSUT2,0A99,FISH01,
> IBMUSER.FISH.TESTFILE.#001
> 09.20.10 JOB00280 IEF234E K 0591,DUMMY ,PVT,FISHGENR
> 09.20.10 JOB00280 IEF404I FISHGENR - ENDED - TIME=09.20.10
>
> The printout is attached.
>
> I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37 REASON CODE=00000004" means, but in the meantime if there's anyone that could provide to this inexperienced newbie any insight on the matter, I'd be *very* grateful.
>
> Thanks.
>
> --
> "Fish" (David B. Trout)
> Software Development Laboratories
> http://www.softdevlabs.com
> mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Abend B37-04

Hercules390 - Mvs mailing list
Sorry replied to the wrong message I meant to reply to your most recent one

Sent from whatever device I am using.

> On Jan 25, 2017, at 8:47 PM, Laddie Hanus [hidden email] [H390-MVS] <[hidden email]> wrote:
>
> Change the block size to 27648. This allows 2 blocks on each track of 27 1024 byte records. Your block size of 30720 only allows 1 block per track wasting the rest of the space. Also for normal datasets the largest they can be is 64K tracks which comes out to 4369 cylinders. Later versions of MVS aka z/OS support  dd parm of DSNTYPE=LARGE but the program writing the data set has to be updated to recognize it. Don't know if iebgener was updated.
>
> Laddie Hanus
>
> Sent from whatever device I am using.
>
>> On Jan 25, 2017, at 8:56 AM, ''Fish' (David B. Trout)' [hidden email] [H390-MVS] <[hidden email]> wrote:
>>
>>  
>> Okay, the following APPEARED to *mostly* work.
>>
>> (By "mostly" I mean it DID start and it DID appear to read my tape.)
>>
>> //FISHGENR JOB 1,FISH,MSGCLASS=X,NOTIFY=&SYSUID
>> // EXEC PGM=IEBGENER
>> //SYSIN DD DUMMY
>> //SYSPRINT DD SYSOUT=*
>> //SYSUT1 DD UNIT=591,LABEL=(,BLP),
>> // DSN=Q.FISHTEST.AWS,VOL=SER=DUMMY,
>> // DISP=(OLD,KEEP,KEEP),
>> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720)
>> //SYSUT2 DD UNIT=A99,VOL=SER=FISH01,
>> // DSN=IBMUSER.FISH.TESTFILE.#001,
>> // SPACE=(CYL,(1000,100)),
>> // DISP=(NEW,KEEP,DELETE),
>> // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=30720,DSORG=PS)
>> //
>>
>> The tape stayed loaded, and "MVS" displayed:
>>
>> 09.17.21 JOB00280 *01 IEF238D FISHGENR - REPLY DEVICE NAME OR 'CANCEL'.
>>
>> So I replied "r 1,591" (the drive my tape was loaded on):
>>
>> 09.19.16 r 1,591
>> 09.19.16 JOB00280 IEE600I REPLY TO 01 IS;591
>>
>> The tape then UNLOADED(!), and "MVS" then displayed:
>>
>> 09.19.16 JOB00280 IEF503I UNIT 0591 INCORRECT VOLUME LABEL
>>
>> and Hercules displayed:
>>
>> HHC00224I 0:0591 Tape file *, type aws: display "D " / "MDUMMY N" (alternating)
>>
>> So I "devinit"ed the drive in Hercules to mount the SAME FREAKING TAPE THAT WAS ALREADY MOUNTED THERE (Sheesh! Why does "MVS" insist on purposely unloading the damn tape I told it to use?! What is UP with that?!), and, miracles of miracles, the job took off running! (Yea!)
>>
>> But the celebration was short lived unfortunately. :(
>>
>> 09.19.16 JOB00280 IEF234E D 0591
>> 09.19.16 JOB00280 *IEF233A M 0591,DUMMY ,,FISHGENR,,Q.FISHTEST.AWS
>> 09.20.10 JOB00280 IEC030I B37-04,IFG0554A,FISHGENR,,SYSUT2,0A99,FISH01,
>> IBMUSER.FISH.TESTFILE.#001
>> 09.20.10 JOB00280 IEF234E K 0591,DUMMY ,PVT,FISHGENR
>> 09.20.10 JOB00280 IEF404I FISHGENR - ENDED - TIME=09.20.10
>>
>> The printout is attached.
>>
>> I'll start digging to try and learn what "SYSTEM COMPLETION CODE=B37 REASON CODE=00000004" means, but in the meantime if there's anyone that could provide to this inexperienced newbie any insight on the matter, I'd be *very* grateful.
>>
>> Thanks.
>>
>> --
>> "Fish" (David B. Trout)
>> Software Development Laboratories
>> http://www.softdevlabs.com
>> mail: [hidden email]
>>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
Laddie Hanus wrote:

> Change the block size to 27648.

No. :)


> This allows 2 blocks on each track of 27 1024 byte records.

I know that.


> Your block size of 30720 only allows 1 block per track wasting
> the rest of the space.

Consuming disk space is one of my goals.


> Also for normal datasets the largest they can be is 64K tracks
> which comes out to 4369 cylinders.

And my dataset appears to be consuming 4350 cylinders.  Last time I checked 4350 < 4369.  Yes?


> Later versions of MVS aka z/OS support  dd parm of DSNTYPE=LARGE
> but the program writing the data set has to be updated to recognize
> it.  Don't know if iebgener was updated.

Since you're not the first person to suggest using a different blocksize I should probably explain my overall goal:

I wish my CCKD defined dasd to grow as close as possible to 4GB in size -- the maximum size currently supported by the Hercules CCKD (Compressed CKD) format.  That's why, as I mentioned in an earlier email, I recreated the tape containing my test data to be 3 times larger than it originally was.  I originally created it with 1GB of random data.  It is now 3GB of random data (which is why it now consumes 4350 cylinders).

I then intend to try loading a differently named dataset (e.g. IBMUSER.FISH.TESTFILE.#002) onto the same Hercules CCKD dasd (UNIT=A99,VOL=SER=FISH01, my 3390-9 test pack) using the same input tape (containing my 3GB worth of random (hopefully uncompressible) test data) to see how Hercules handles it.

I suspect that Hercules's CCKD logic will cause a crash to occur, but do not know for sure.  I have not studied the code that closely.  I figured it would be faster and easier to just try it and see what happens.

If it crashes, then I can debug the problem and hopefully fix it.

If it doesn't crash, then I would like to learn why.  I would like to learn how Greg's CCKD logic handles such a situation.  Does it issue an error message and force an Equipment Check I/O error?  Should it maybe instead force the creation of a new shadow file? (presuming support for one was specified)  What if the maximum number of shadow files has already been reached? (currently 8)  Should that limit be increased?  Or even better, removed completely? (i.e. unlimited number of shadow files)

Etc.

Sooo... I *don't* wish to be efficient.  I *do* wish to consume lots of disk space.

But setting all of that aside for the moment, NONE of this answers my original question of WHY am I still experiencing a B37-04 (Out of Space (presumably)) abend?!  The drive is a 3390-9!  It has 10017 cylinders!  (Of which I am only consuming 4350 of them)

Why is the B37-04 abend still occurring?

Thanks for any insight.

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [hidden email]




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
Fish wrote:

[...]
> But setting all of that aside for the moment, NONE of this
> answers my original question of WHY am I still experiencing
> a B37-04 (Out of Space (presumably)) abend?!  The drive is
> a 3390-9!  It has 10017 cylinders!  (Of which I am only
> consuming 4350 of them)
>
> Why is the B37-04 abend still occurring?

Okay, I think I know what's going on now.  Sorry about that Laddie.  You tried to tell me but it didn't sink in the first time.

Please see my subsequent reply to [hidden email].

Thanks!

(and sorry about that!)

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [hidden email]




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
[repost, yahoo is taking its time again]


---In [hidden email], <david.b.trout@...> wrote :

>> Your block size of 30720 only allows 1 block per track wasting
>> the rest of the space.

> Consuming disk space is one of my goals.

If you set the block size to 28672, that
will create the maximum waste possible.

>> Also for normal datasets the largest they can be is 64K tracks
>> which comes out to 4369 cylinders.

> And my dataset appears to be consuming 4350
> cylinders. Last time I checked 4350 < 4369. Yes?

Yes, but as you already acknowledged,
you can't get an extra extent and still
be within that limit.

> I wish my CCKD defined dasd to grow as
> close as possible to 4GB in size

You're interested in the size of the
*compressed* file? If so, wasting
space on every track by having
NULs, or nothing, there, will not
get you closer to your goal. Filling
up the track entirely with the
recommended block size will get
you closer to 4 GiB with each file
added.

> But setting all of that aside for the
> moment, NONE of this answers my
> original question of WHY am I still
> experiencing a B37-04 (Out of
> Space (presumably)) abend?! The
> drive is a 3390-9! It has 10017
> cylinders! (Of which I am only
> consuming 4350 of them)

> Why is the B37-04 abend still occurring?

What message would you like to see that
says "sorry, I am unable to add another
extent because that would take it over
the 4369 limit"? IBM doesn't produce
messages like that.

BFN. Paul.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Abend B37-04

Hercules390 - Mvs mailing list
In reply to this post by Hercules390 - Mvs mailing list
---In [hidden email], <david.b.trout@...> wrote :

>> Your block size of 30720 only allows 1 block per track wasting
>> the rest of the space.

> Consuming disk space is one of my goals.

If you set the block size to 28672, that
will create the maximum waste possible.

>> Also for normal datasets the largest they can be is 64K tracks
>> which comes out to 4369 cylinders.

> And my dataset appears to be consuming 4350
> cylinders. Last time I checked 4350 < 4369. Yes?

Yes, but as you already acknowledged,
you can't get an extra extent and still
be within that limit.

> I wish my CCKD defined dasd to grow as
> close as possible to 4GB in size

You're interested in the size of the
*compressed* file? If so, wasting
space on every track by having
NULs, or nothing, there, will not
get you closer to your goal. Filling
up the track entirely with the
recommended block size will get
you closer to 4 GiB with each file
added.

> But setting all of that aside for the
> moment, NONE of this answers my
> original question of WHY am I still
> experiencing a B37-04 (Out of
> Space (presumably)) abend?! The
> drive is a 3390-9! It has 10017
> cylinders! (Of which I am only
> consuming 4350 of them)

> Why is the B37-04 abend still occurring?

What message would you like to see that
says "sorry, I am unable to add another
extent because that would take it over
the 4369 limit"? IBM doesn't produce
messages like that.

BFN. Paul.
Loading...