Re: Possible Debug issue

2017-12-13 Thread Seymour J Metz 
REGION=0M might even give you less than the default region; you really need to 
know what your installation's exits are doing.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List  on behalf of 
Frank Swarbrick 
Sent: Wednesday, December 13, 2017 2:10 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Possible Debug issue

I seem to recall trying REGION=0M not working in this case.  Over-allocation or 
something.  Can't recall the details.  Perhaps I imagined it?

From: IBM Mainframe Discussion List  on behalf of 
Peter Hunkeler 
Sent: Tuesday, December 12, 2017 11:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: Possible Debug issue

>Debug Tool and Fault Analyzer seem to take a huge amount of memory when 
>working with COBOL 5.  Try setting REGION=2000M.


What release of z/OS managed to move the whole common area above the bar?
Seriously, 2000M will probably never be available in the private region. But if 
you want to see how much you need to be able to debug, within the maximum 
available, specify REGION=0M.


--
Peter Hunkeler





--
Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Frank Swarbrick 
If you have the ability to open an SR regarding this, could you do so?  I have 
to go through my sysprogs to do so, so if someone else was to do it instead it 
would be very convenient for me.  :-)

From: IBM Mainframe Discussion List  on behalf of 
Savor, Thomas (Alpharetta) 
Sent: Wednesday, December 13, 2017 12:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

I tried 2000M...didnt get the errors.  I will pass it on to the tester.

Here is what 2000M gave me:
IEF032I STEP/EP2999  /STOP  2017345.1758
CPU: 0 HR  00 MIN  00.15 SECSRB: 0 HR  00 MIN  00.02 SEC
VIRT:   412K  SYS:   336K  EXT:28256K  SYS:11532K
ATB- REAL:   208K  SLOTS: 0K
 VIRT- ALLOC:  21M SHRD:   0M



Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com<http://www.fiserv.com>



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Wednesday, December 13, 2017 10:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

Depending on you IEFUSI or other functions used to control region size, you may 
not be getting what you think 0M gives you.

If you try the suggestion of 2000M for region and rerun the job, what do you 
get?

If you have an ACTRT exit in your shop - it may provide the virtual storage map 
at step end. There you should the Requested/Below/above/ and so forth of 
storage allocation for the step.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Savor, Thomas (Alpharetta)
> Sent: Tuesday, December 12, 2017 11:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Possible Debug issue
>
> On this particular test that got all the storage error
> messages..region was set to 0M
>
> Thanks,
>
> Tom Savor
> Software Developer, Sr
> FRMS-SCM
> Fiserv
> Office:  678-375-1307
> Mobile: 404-660-6898
> Fax:  678-375-3280
> www.fiserv.com<http://www.fiserv.com>
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Peter Hunkeler
> Sent: Wednesday, December 13, 2017 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: Possible Debug issue
>
> >Debug Tool and Fault Analyzer seem to take a huge amount of memory
> >when
> working with COBOL 5.  Try setting REGION=2000M.
>
>
> What release of z/OS managed to move the whole common area above the bar?
> Seriously, 2000M will probably never be available in the private
> region. But if you want to see how much you need to be able to debug,
> within the maximum available, specify REGION=0M.
>
>
> --
> Peter Hunkeler
>
>
>
>
>
> --
> Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Frank Swarbrick 
I seem to recall trying REGION=0M not working in this case.  Over-allocation or 
something.  Can't recall the details.  Perhaps I imagined it?

From: IBM Mainframe Discussion List  on behalf of 
Peter Hunkeler 
Sent: Tuesday, December 12, 2017 11:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: Possible Debug issue

>Debug Tool and Fault Analyzer seem to take a huge amount of memory when 
>working with COBOL 5.  Try setting REGION=2000M.


What release of z/OS managed to move the whole common area above the bar?
Seriously, 2000M will probably never be available in the private region. But if 
you want to see how much you need to be able to debug, within the maximum 
available, specify REGION=0M.


--
Peter Hunkeler





--
Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Savor, Thomas (Alpharetta) 
I tried 2000M...didnt get the errors.  I will pass it on to the tester.

Here is what 2000M gave me:
IEF032I STEP/EP2999  /STOP  2017345.1758   
CPU: 0 HR  00 MIN  00.15 SECSRB: 0 HR  00 MIN  00.02 SEC   
VIRT:   412K  SYS:   336K  EXT:28256K  SYS:11532K  
ATB- REAL:   208K  SLOTS: 0K   
 VIRT- ALLOC:  21M SHRD:   0M  



Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Wednesday, December 13, 2017 10:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

Depending on you IEFUSI or other functions used to control region size, you may 
not be getting what you think 0M gives you.

If you try the suggestion of 2000M for region and rerun the job, what do you 
get?

If you have an ACTRT exit in your shop - it may provide the virtual storage map 
at step end. There you should the Requested/Below/above/ and so forth of 
storage allocation for the step.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Savor, Thomas (Alpharetta)
> Sent: Tuesday, December 12, 2017 11:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Possible Debug issue
> 
> On this particular test that got all the storage error 
> messages..region was set to 0M
> 
> Thanks,
> 
> Tom Savor
> Software Developer, Sr
> FRMS-SCM
> Fiserv
> Office:  678-375-1307
> Mobile: 404-660-6898
> Fax:  678-375-3280
> www.fiserv.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Peter Hunkeler
> Sent: Wednesday, December 13, 2017 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: Possible Debug issue
> 
> >Debug Tool and Fault Analyzer seem to take a huge amount of memory 
> >when
> working with COBOL 5.  Try setting REGION=2000M.
> 
> 
> What release of z/OS managed to move the whole common area above the bar?
> Seriously, 2000M will probably never be available in the private 
> region. But if you want to see how much you need to be able to debug, 
> within the maximum available, specify REGION=0M.
> 
> 
> --
> Peter Hunkeler
> 
> 
> 
> 
> 
> --
> Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Savor, Thomas (Alpharetta) 
This is what REGION=0M gave me:
IEF032I STEP/EP2999  /STOP  2017345.1334   
CPU: 0 HR  01 MIN  18.18 SECSRB: 0 HR  00 MIN  00.0
VIRT: 10492K  SYS:   512K  EXT:  1735996K  SYS:11932K  
ATB- REAL:   120K  SLOTS: 0
 VIRT- ALLOC:  20M SHRD:   0M  

Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Barry Merrill
Sent: Wednesday, December 13, 2017 1:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

The IEF032I Joblog Message

IEF032I STEP/SAS9/STOP  2017344.2055
CPU: 0 HR  00 MIN  00.67 SECSRB: 0 HR  00 MIN  00.02 SEC
VIRT:   912K  SYS:   292K  EXT:46616K  SYS:11788K
ATB- REAL:  1044K  SLOTS: 0K
 VIRT- ALLOC:  11M SHRD:   0M

has the REGION SIZE allocated in the sum of the EXT + SYS  = 46616K+11788K= 
58404K = 57 MegaBytes

Barry


Merrilly yours,

 Herbert W. Barry Merrill, PhD
 President-Programmer
 Merrill Consultants
 MXG Software
 10717 Cromwell Drive  technical questions: supp...@mxg.com
 Dallas, TX 75229
 http://www.mxg.comadmin questions: ad...@mxg.com
 tel: 214 351 1966
 fax: 214 350 3694




-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Wednesday, December 13, 2017 9:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

Depending on you IEFUSI or other functions used to control region size, you may 
not be getting what you think 0M gives you.

If you try the suggestion of 2000M for region and rerun the job, what do you 
get?

If you have an ACTRT exit in your shop - it may provide the virtual storage map 
at step end. There you should the Requested/Below/above/ and so forth of 
storage allocation for the step.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Savor, Thomas (Alpharetta)
> Sent: Tuesday, December 12, 2017 11:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Possible Debug issue
> 
> On this particular test that got all the storage error 
> messages..region was set to 0M
> 
> Thanks,
> 
> Tom Savor
> Software Developer, Sr
> FRMS-SCM
> Fiserv
> Office:  678-375-1307
> Mobile: 404-660-6898
> Fax:  678-375-3280
> www.fiserv.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Peter Hunkeler
> Sent: Wednesday, December 13, 2017 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: Possible Debug issue
> 
> >Debug Tool and Fault Analyzer seem to take a huge amount of memory 
> >when
> working with COBOL 5.  Try setting REGION=2000M.
> 
> 
> What release of z/OS managed to move the whole common area above the bar?
> Seriously, 2000M will probably never be available in the private 
> region. But if you want to see how much you need to be able to debug, 
> within the maximum available, specify REGION=0M.
> 
> 
> --
> Peter Hunkeler
> 
> 
> 
> 
> 
> --
> Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Barry Merrill 
The IEF032I Joblog Message

IEF032I STEP/SAS9/STOP  2017344.2055
CPU: 0 HR  00 MIN  00.67 SECSRB: 0 HR  00 MIN  00.02 SEC
VIRT:   912K  SYS:   292K  EXT:46616K  SYS:11788K
ATB- REAL:  1044K  SLOTS: 0K
 VIRT- ALLOC:  11M SHRD:   0M

has the REGION SIZE allocated in the sum of the EXT + SYS  = 46616K+11788K=
58404K = 57 MegaBytes

Barry


Merrilly yours,

 Herbert W. Barry Merrill, PhD
 President-Programmer
 Merrill Consultants
 MXG Software
 10717 Cromwell Drive  technical questions: supp...@mxg.com
 Dallas, TX 75229
 http://www.mxg.comadmin questions: ad...@mxg.com
 tel: 214 351 1966
 fax: 214 350 3694




-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lizette Koehler
Sent: Wednesday, December 13, 2017 9:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

Depending on you IEFUSI or other functions used to control region size, you
may not be getting what you think 0M gives you.

If you try the suggestion of 2000M for region and rerun the job, what do you
get?

If you have an ACTRT exit in your shop - it may provide the virtual storage
map at step end. There you should the Requested/Below/above/ and so forth of
storage allocation for the step.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Savor, Thomas (Alpharetta)
> Sent: Tuesday, December 12, 2017 11:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Possible Debug issue
> 
> On this particular test that got all the storage error 
> messages..region was set to 0M
> 
> Thanks,
> 
> Tom Savor
> Software Developer, Sr
> FRMS-SCM
> Fiserv
> Office:  678-375-1307
> Mobile: 404-660-6898
> Fax:  678-375-3280
> www.fiserv.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Peter Hunkeler
> Sent: Wednesday, December 13, 2017 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: Possible Debug issue
> 
> >Debug Tool and Fault Analyzer seem to take a huge amount of memory 
> >when
> working with COBOL 5.  Try setting REGION=2000M.
> 
> 
> What release of z/OS managed to move the whole common area above the bar?
> Seriously, 2000M will probably never be available in the private 
> region. But if you want to see how much you need to be able to debug, 
> within the maximum available, specify REGION=0M.
> 
> 
> --
> Peter Hunkeler
> 
> 
> 
> 
> 
> --
> Peter Hunkeler

--
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

Re: Possible Debug issue

2017-12-13 Thread Farley, Peter x23353 
Double check with your systems team whether REGION=0M actually gets you 0M.  
IEFUSI exit can change that to whatever they want to limit your job to use.

Some shops have "bypass" step names that tell IEFUSI not to enforce rules for 
that step, "just do what I say".  Some require SAF authorization for the user 
running the job to bypass the rules.  YMMV

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Savor, Thomas (Alpharetta)
Sent: Wednesday, December 13, 2017 1:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Possible Debug issue

On this particular test that got all the storage error messages..region was 
set to 0M

Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Hunkeler
Sent: Wednesday, December 13, 2017 1:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: Possible Debug issue

>Debug Tool and Fault Analyzer seem to take a huge amount of memory when 
>working with COBOL 5.  Try setting REGION=2000M. 


What release of z/OS managed to move the whole common area above the bar?
Seriously, 2000M will probably never be available in the private region. But if 
you want to see how much you need to be able to debug, within the maximum 
available, specify REGION=0M. 


--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

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

Re: Possible Debug issue

2017-12-13 Thread Lizette Koehler 
Depending on you IEFUSI or other functions used to control region size, you may
not be getting what you think 0M gives you.

If you try the suggestion of 2000M for region and rerun the job, what do you
get?

If you have an ACTRT exit in your shop - it may provide the virtual storage map
at step end. There you should the Requested/Below/above/ and so forth of storage
allocation for the step.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Savor, Thomas (Alpharetta)
> Sent: Tuesday, December 12, 2017 11:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Possible Debug issue
> 
> On this particular test that got all the storage error messages..region
> was set to 0M
> 
> Thanks,
> 
> Tom Savor
> Software Developer, Sr
> FRMS-SCM
> Fiserv
> Office:  678-375-1307
> Mobile: 404-660-6898
> Fax:  678-375-3280
> www.fiserv.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Hunkeler
> Sent: Wednesday, December 13, 2017 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: Re: Possible Debug issue
> 
> >Debug Tool and Fault Analyzer seem to take a huge amount of memory when
> working with COBOL 5.  Try setting REGION=2000M.
> 
> 
> What release of z/OS managed to move the whole common area above the bar?
> Seriously, 2000M will probably never be available in the private region. But
> if you want to see how much you need to be able to debug, within the maximum
> available, specify REGION=0M.
> 
> 
> --
> Peter Hunkeler
> 
> 
> 
> 
> 
> --
> Peter Hunkeler

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

Re: Possible Debug issue

2017-12-12 Thread Savor, Thomas (Alpharetta) 
On this particular test that got all the storage error messages..region was 
set to 0M

Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Peter Hunkeler
Sent: Wednesday, December 13, 2017 1:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: Possible Debug issue

>Debug Tool and Fault Analyzer seem to take a huge amount of memory when 
>working with COBOL 5.  Try setting REGION=2000M. 


What release of z/OS managed to move the whole common area above the bar?
Seriously, 2000M will probably never be available in the private region. But if 
you want to see how much you need to be able to debug, within the maximum 
available, specify REGION=0M. 


--
Peter Hunkeler





--
Peter Hunkeler 

--
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

AW: Re: Possible Debug issue

2017-12-12 Thread Peter Hunkeler 
>Debug Tool and Fault Analyzer seem to take a huge amount of memory when 
>working with COBOL 5.  Try setting REGION=2000M.


What release of z/OS managed to move the whole common area above the bar?
Seriously, 2000M will probably never be available in the private region. But if 
you want to see how much you need to be able to debug, within the maximum 
available, specify REGION=0M.


--
Peter Hunkeler





--
Peter Hunkeler

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

Re: Possible Debug issue

2017-12-12 Thread Frank Swarbrick 
Debug Tool and Fault Analyzer seem to take a huge amount of memory when working 
with COBOL 5.  Try setting REGION=2000M.

From: IBM Mainframe Discussion List  on behalf of 
Savor, Thomas (Alpharetta) 
Sent: Tuesday, December 12, 2017 8:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Possible Debug issue

Anybody ever get this when running a COBOL 5 program under Debug ??

13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.48 JOB70977  +IEW2971T C406 INSUFFICIENT ABOVE THE LINE STORAGE WAS 
AVAILABLE TO CONTINUE
 13.34.48 JOB70977  + BINDER PROCESSING.
 13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CEEMENU3 FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CEEMENU3, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL

Without Debug, no issues.
Never heard or seen these messages before.


Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com<http://www.fiserv.com/>



--
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

Re: Possible Debug issue

2017-12-12 Thread John Eells 
I have no experience with COBOL, but I would surmise that running under 
Debug requires additional programs to be loaded and that the specified 
REGION is too small to contain them in addition to the program or 
programs you are trying to run.


What do you have specified for REGION?  Is there some reason not to 
increase it?



Savor, Thomas , Alpharetta wrote:

Anybody ever get this when running a COBOL 5 program under Debug ??

13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
  13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
  13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
  13.34.48 JOB70977  +IEW2971T C406 INSUFFICIENT ABOVE THE LINE STORAGE WAS 
AVAILABLE TO CONTINUE
  13.34.48 JOB70977  + BINDER PROCESSING.
  13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CEEMENU3 FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CEEMENU3, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL

Without Debug, no issues.
Never heard or seen these messages before.



--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

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

Possible Debug issue

2017-12-12 Thread Savor, Thomas (Alpharetta) 
Anybody ever get this when running a COBOL 5 program under Debug ??

13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.47 JOB70977  +IEW2974T C008 REGION TOO SMALL TO ESTABLISH BINDER 
ENVIRONMENT.
 13.34.48 JOB70977  +IEW2971T C406 INSUFFICIENT ABOVE THE LINE STORAGE WAS 
AVAILABLE TO CONTINUE
 13.34.48 JOB70977  + BINDER PROCESSING.
 13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CEEMENU3 FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CEEMENU3, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL
13.34.48 JOB70977  CSV031I LIBRARY ACCESS FAILED FOR MODULE CBCDEBUG, RETURN 
CODE 24, REASON CODE 26080021, DDNAME *LNKLST*
13.34.48 JOB70977  IEW4000I FETCH FOR MODULE CBCDEBUG FROM DDNAME -LNKLST- 
FAILED BECAUSE INSUFFICIENT STORAGE WAS AVAILABL

Without Debug, no issues.
Never heard or seen these messages before.


Thanks,

Tom Savor
Software Developer, Sr
FRMS-SCM
Fiserv
Office:  678-375-1307
Mobile: 404-660-6898
Fax:  678-375-3280
www.fiserv.com



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