Discussion:
SIZE= parm on a cobol program exec
(too old to reply)
Randy Dray
20 years ago
Permalink
We have a very large program that we just added 3 new
files.

at execution time we put in

size=512 on the execution and it blows up with this
message

BG 0000 0S35I PHASE ILUSMANR DOES NOT FIT IN LTA OR
PARTITION


to fix this I just keep increasing the size untill it
works.

for this example I used SIZE=920 and it worked.

Question: How can I tell the largest program that I
can load into each partition.

If i do a map bg at the console i get

PARTITION: BG SPACE-GETVIS......: (N/A)
SPACE....: 0 ALLOC (VIRTUAL)...: 6144K
STATUS...: VIRTUAL SIZE............: 1280K
POWER-JOB:
JOBNUMBER: GETVIS..........: 4864K
JOBNAME..:
PHASE....:
PFIX(BELOW)-LIMIT : 0K
-ACTUAL: 0K
PFIX(ABOVE)-LIMIT : 0K


How do I know how much a program really needs.

CONSOLE COMMAND???



Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Rich Smrcina
20 years ago
Permalink
SIZE=AUTO is usually pretty safe. The problem is that your program uses
an internal sort and your fave SORT product also needs to fit some of
it's code into the program area, which is why you had to allocate extra.

The largest program that can fit is the size of the partition -48K (I
think). Some storage is required for minimal buffering for VSAM files
and the like.

You're pretty safe using SIZE=AUTO unless you need to provide extra.
...
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
Randy Dray
20 years ago
Permalink
Thanks Rich,

By your example I can issue a map Fn

take the size (which is 1280k) and subtract 48

1280 - 48 = 1232

so size=1232 is the biggest I could go.



Thanks,
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Rich Smrcina
20 years ago
Permalink
That looks like 1280K might be the default SIZE. This is the value that
is used when no SIZE parameter is specified. You want the partition
size, the ALLOC value in the MAP xx command.
...
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
Ken Meyer
20 years ago
Permalink
No. SIZE is the default value if you do not specify one:

// EXEC PROGRAM

The largest for that partition would be 6144-48 (approx.)
or 6096K

Ken Meyer
CSI
Post by Randy Dray
Thanks Rich,
By your example I can issue a map Fn
take the size (which is 1280k) and subtract 48
1280 - 48 = 1232
so size=1232 is the biggest I could go.
snip..
Randy Dray
20 years ago
Permalink
Ah!!

I take the ALLOC from the MAP xx command and subtract
48 from that. this is the max for the size of program
I can execute in this spacific partition.

Thank you for the info.


What is 48 all about?
Post by Ken Meyer
No. SIZE is the default value if you do not specify
// EXEC PROGRAM
The largest for that partition would be 6144-48
(approx.)
or 6096K
Ken Meyer
CSI
Post by Randy Dray
Thanks Rich,
By your example I can issue a map Fn
take the size (which is 1280k) and subtract 48
1280 - 48 = 1232
so size=1232 is the biggest I could go.
snip..
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Steve Sheerin
20 years ago
Permalink
The other option is to add some extra space for the sort like this:

// EXEC ACR105,SIZE=(AUTO,256K)

This is what we use for some of our larger internal SORT programs..

Steve Sheerin

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf
Of Rich Smrcina
Sent: Wednesday, July 27, 2005 11:28 AM
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec

SIZE=AUTO is usually pretty safe. The problem is that your program uses

an internal sort and your fave SORT product also needs to fit some of
it's code into the program area, which is why you had to allocate extra.

The largest program that can fit is the size of the partition -48K (I
think). Some storage is required for minimal buffering for VSAM files
and the like.

You're pretty safe using SIZE=AUTO unless you need to provide extra.
...
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Imholte, John , Cincinnati, OH
20 years ago
Permalink
And just one more way of doing this...

// EXEC ACR105,SIZE=(ACR105,256K)

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU]On Behalf Of
Steve Sheerin
Sent: Wednesday, July 27, 2005 2:39 PM
To: VSE Discussion List
Subject: RE: SIZE= parm on a cobol program exec


The other option is to add some extra space for the sort like this:

// EXEC ACR105,SIZE=(AUTO,256K)

This is what we use for some of our larger internal SORT programs..

Steve Sheerin

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf
Of Rich Smrcina
Sent: Wednesday, July 27, 2005 11:28 AM
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec

SIZE=AUTO is usually pretty safe. The problem is that your program uses

an internal sort and your fave SORT product also needs to fit some of
it's code into the program area, which is why you had to allocate extra.

The largest program that can fit is the size of the partition -48K (I
think). Some storage is required for minimal buffering for VSAM files
and the like.

You're pretty safe using SIZE=AUTO unless you need to provide extra.
...
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
r***@aol.com
20 years ago
Permalink
I think the preferred way is:

// EXEC PROGNAME,SIZE=PROGNAME

If an internal sort is used, then:

// EXEC PROGNAME,SIZE=(PROGNAME,nnnK)

-----Original Message-----
From: Imholte, John (Cincinnati, OH) <***@unisource.ca>
To: VSE Discussion List <vse-***@Lehigh.EDU>
Sent: Wed, 27 Jul 2005 14:41:38 -0400
Subject: RE: SIZE= parm on a cobol program exec

And just one more way of doing this...

// EXEC ACR105,SIZE=(ACR105,256K)

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU]On Behalf Of
Steve Sheerin
Sent: Wednesday, July 27, 2005 2:39 PM
To: VSE Discussion List
Subject: RE: SIZE= parm on a cobol program exec


The other option is to add some extra space for the sort like this:

// EXEC ACR105,SIZE=(AUTO,256K)

This is what we use for some of our larger internal SORT programs..

Steve Sheerin

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf
Of Rich Smrcina
Sent: Wednesday, July 27, 2005 11:28 AM
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec

SIZE=AUTO is usually pretty safe. The problem is that your program uses

an internal sort and your fave SORT product also needs to fit some of
it's code into the program area, which is why you had to allocate extra.

The largest program that can fit is the size of the partition -48K (I
think). Some storage is required for minimal buffering for VSAM files
and the like.

You're pretty safe using SIZE=AUTO unless you need to provide extra.
...
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com

Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Tony Thigpen
20 years ago
Permalink
With later versions (VSE 2.7 and higher), the preferred way would be:
// EXEC PROGNAME,SIZE=*
// EXEC PROGNAME,SIZE=(*,nnnK)
Less prone to error or typos.

Tony Thigpen


-----Original Message -----
From: ***@aol.com
Sent: 07/27/2005 02:45 PM
...
Frank M. Ramaekers
20 years ago
Permalink
Typically, we use:

// EXEC program,SIZE=program

Frank M. Ramaekers Jr.
Systems Programmer
American Income Life Insurance Company
Phone: (254) 761-6649

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf
Of Randy Dray
Sent: Wednesday, July 27, 2005 1:31 PM
To: VSE Discussion List
Subject: SIZE= parm on a cobol program exec

We have a very large program that we just added 3 new
files.

at execution time we put in

size=512 on the execution and it blows up with this
message

BG 0000 0S35I PHASE ILUSMANR DOES NOT FIT IN LTA OR
PARTITION


to fix this I just keep increasing the size untill it
works.

for this example I used SIZE=920 and it worked.

Question: How can I tell the largest program that I
can load into each partition.

If i do a map bg at the console i get

PARTITION: BG SPACE-GETVIS......: (N/A)
SPACE....: 0 ALLOC (VIRTUAL)...: 6144K
STATUS...: VIRTUAL SIZE............: 1280K
POWER-JOB:
JOBNUMBER: GETVIS..........: 4864K
JOBNAME..:
PHASE....:
PFIX(BELOW)-LIMIT : 0K
-ACTUAL: 0K
PFIX(ABOVE)-LIMIT : 0K


How do I know how much a program really needs.

CONSOLE COMMAND???



Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs



----------------------------------------
This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at ***@ailife.com.
Edward M. Martin
20 years ago
Permalink
Hello Randy and everyone else,

Some insights and request for comments.

Figuring out the size of the partition need for a program.

From the linkedt map I have
ENTRY

07/27/2005 PHASE XFR-AD LOCORE HICORE
KP593BC 600078 600078 64A59F

Which gives 4A527 (304423 bytes) about 298k


And from the compile listing I have

WRK-STOR WILL BE ALLOCATED FOR 001B7438 BYTES

Which is 1758kb

And requirements for each VSAM file it opens up. 16k per catalog and 8k
per file plus buffers.
And the 48k system requirement.

This program would need at least 2104k minimum.
Plus size for internal sort (if it had one)
And if you add more files you would need more space.

Does this seem correct?

Ed Martin
Aultman Health Foundation
330-363-5050
***@aultman.com
David Stuart
20 years ago
Permalink
Randy,

You must leave at least 48K (64K is safer) in the partition for Job
Control and System work areas.
If you don't, all kinds of interesting, mostly bad things can happen.



Dave



Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
Ah!!

I take the ALLOC from the MAP xx command and subtract
48 from that. this is the max for the size of program
I can execute in this spacific partition.

Thank you for the info.


What is 48 all about?
Post by Ken Meyer
No. SIZE is the default value if you do not specify
// EXEC PROGRAM
The largest for that partition would be 6144-48
(approx.)
or 6096K
Ken Meyer
CSI
Post by Randy Dray
Thanks Rich,
By your example I can issue a map Fn
take the size (which is 1280k) and subtract 48
1280 - 48 = 1232
so size=1232 is the biggest I could go.
snip..
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Randy Dray
20 years ago
Permalink
I tried SIZE=AUTO and I go the error


DLZ058I INSUFFICIENT STORAGE TO START DL/I


Still I found SIZE=920 to work.

I am looking into ED's example,

but getting complex

has lots of files(11), lots sort files (internal 5)
and is a big DLI program, 1 DB with thousands of calls
to lots of different segments.

Thanks,
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Kevin Corkery
20 years ago
Permalink
Randy ...

Now this is very shop dependent based on your virtual and real resources but
I have found that fine tuning the default basically permits most batch
applications to run without concern for the SIZE parameter. The use of the
SIZE on the EXEC card should be a rare occurance. The trick to to create a
batch partition of sufficient size to accommodate both the loading of
programs, sort usage, and leave enough getvis for buffer allocations. For
instance, in one shop all the production partitions are 10MB with the SIZE
set to 4MB. This leaves 6MB for VSAM buffers. CA-SORT has plenty of space
below the getvis line for sorting (it will also use some above the getvis
line depending on setup limitations). The "wasted" space when not sorting
is all virtual anyway. This was set up this way a long time ago so that the
programmers could just ignore dealing with the SIZE parameter. Of course,
each environment has it's own constraints, but if you can generalize you can
save a good deal of work.

Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
Randy Dray
20 years ago
Permalink
Thanks Kevin,

Where do I look to find the default size? I removed
the SIZE=960 from the offending program and it ran
fine. I assume that the default is big enough. I
need to look at the real default, the people watching
are real sticklers for EXACT reasons. NO room here
for "cus I said so". They want proof and will go to
great lengths to trash it, especialy the testers. Not
complaining, keeps me on my toes.

Thanks
Post by Kevin Corkery
Randy ...
Now this is very shop dependent based on your
virtual and real resources but
I have found that fine tuning the default basically
permits most batch
applications to run without concern for the SIZE
parameter. The use of the
SIZE on the EXEC card should be a rare occurance.
The trick to to create a
snip .........



Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Michael Rosinger
20 years ago
Permalink
Randy,

I agree with everyone that's suggested // EXEC program,SIZE=program. If you
are on 2.7.x or z/VSE 3.1, then Tony's suggestion of SIZE=* is even better,
since it avoids the "typo" problem. If you hardcode a number for the size in
your jobs, you have to make sure you adjust it appropriately if the program
changes in any significant way.
...
Edward M. Martin
20 years ago
Permalink
Hello Randy,

Sorry most everything that has been said is now in question.
I have worked with DL/1 (DL/I) some.

Are you allowed to show the // exec dlzmpi00/dlzrrc0?
And the DL/1 statements after that?

The example everyone gave was a straight COBOL/Assembler
program.
DL/1 loads the program into a different area and loads DL/1 stuff and
other things. So the size calculation is different.

Ed Martin
Aultman Health Foundation
330-363-5050
***@aultman.com
Allan Peterson
20 years ago
Permalink
// EXEC DLZRRC00,SIZE=4M 00005
DLI,DLYB001,DLIPDLY,4,HDBFR=(32),HDBFR=(32),HDBFR=(32),HDBFR=(32) - 00005
,RC=YES 00005

The size must allow for the program , the PSB , the buffers ....

I cannot recall any of our DL/I having size=auto


Allan

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU]On Behalf Of
Randy Dray
Sent: Thursday, 28 July 2005 7:45 a.m.
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec


I tried SIZE=AUTO and I go the error


DLZ058I INSUFFICIENT STORAGE TO START DL/I


Still I found SIZE=920 to work.

I am looking into ED's example,

but getting complex

has lots of files(11), lots sort files (internal 5)
and is a big DLI program, 1 DB with thousands of calls
to lots of different segments.

Thanks,
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
R***@aol.com
20 years ago
Permalink
<<With later versions (VSE 2.7 and higher), the preferred way would be:
// EXEC PROGNAME,SIZE=*
// EXEC PROGNAME,SIZE=(*,nnnK)
Less prone to error or typos.>>

Yup, I agree using an asterisk would be mucho better. I must've (did) missed
that change.



Robert Botsis
Kroger Co.
513-745-5487
(I read and I remember,
I do and I understand)
David Stuart
20 years ago
Permalink
Size=AUTO reset the size of the partition to the size of the largest
phase which has the same first four characters as specified on the //
EXEC statement.

In the case of a COBOL program with a Sort, that obviously will not
work, unless there is another COBOL program that starts with the same
first four characters that is sufficiently large enough to accommodate
the sort. This probably applies to DL/I as well, what with all the
buffers, PSB('s), etc., and others.

For programs such as COBOL with a Sort, a // EXEC
progname,SIZE=(AUTO,256K), or something similar, then AUTO will work, as
JCL will add an additional 256K (or whatever is specified) to the size
determined from the largest phase with the same first 4 characters of
the phase name. SIZE=(AUTO,xxxK|M) *might* (emphasize might) work for
DL/I, if the additional space was specified large enough.



Dave



Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
// EXEC DLZRRC00,SIZE=4M
00005
DLI,DLYB001,DLIPDLY,4,HDBFR=(32),HDBFR=(32),HDBFR=(32),HDBFR=(32)
- 00005
,RC=YES
00005

The size must allow for the program , the PSB , the buffers ....

I cannot recall any of our DL/I having size=auto


Allan

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU]On Behalf
Of
Randy Dray
Sent: Thursday, 28 July 2005 7:45 a.m.
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec


I tried SIZE=AUTO and I go the error


DLZ058I INSUFFICIENT STORAGE TO START DL/I


Still I found SIZE=920 to work.

I am looking into ED's example,

but getting complex

has lots of files(11), lots sort files (internal 5)
and is a big DLI program, 1 DB with thousands of calls
to lots of different segments.

Thanks,
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
David Stuart
20 years ago
Permalink
Randy,

When you allocate a partition at IPL/ASI time, there are two
specifications:

ALLOC Fx,10M This sets the total partition
size.
SIZE Fx,2048K This sets the default size of
the partition, if no SIZE= is specified on the // EXEC card.



Dave



Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
Thanks Kevin,

Where do I look to find the default size? I removed
the SIZE=960 from the offending program and it ran
fine. I assume that the default is big enough. I
need to look at the real default, the people watching
are real sticklers for EXACT reasons. NO room here
for "cus I said so". They want proof and will go to
great lengths to trash it, especialy the testers. Not
complaining, keeps me on my toes.

Thanks
Post by Kevin Corkery
Randy ...
Now this is very shop dependent based on your
virtual and real resources but
I have found that fine tuning the default basically
permits most batch
applications to run without concern for the SIZE
parameter. The use of the
SIZE on the EXEC card should be a rare occurance.
The trick to to create a
snip .........



Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Kevin Corkery
20 years ago
Permalink
Additionally, in the "Maintain Dynamic Classes" dialog there is the
equivalent entries for your dynamic partitions.
You can use the POWER "D DYNC" command to get the current definitions and
the AR "MAP XX" where XX is the static partition to get the defaults for
your static partitions.

Kevin P Corkery
Independent Consultant
Voorhees, New Jersey

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf Of
David Stuart
Sent: Thursday, July 28, 2005 12:02 PM
To: VSE Discussion List
Subject: RE: SIZE= parm on a cobol program exec


Randy,

When you allocate a partition at IPL/ASI time, there are two
specifications:

ALLOC Fx,10M This sets the total partition
size.
SIZE Fx,2048K This sets the default size of
the partition, if no SIZE= is specified on the // EXEC card.



Dave



Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
Thanks Kevin,

Where do I look to find the default size? I removed
the SIZE=960 from the offending program and it ran
fine. I assume that the default is big enough. I
need to look at the real default, the people watching
are real sticklers for EXACT reasons. NO room here
for "cus I said so". They want proof and will go to
great lengths to trash it, especialy the testers. Not complaining, keeps me
on my toes.

Thanks
Post by Kevin Corkery
Randy ...
Now this is very shop dependent based on your
virtual and real resources but
I have found that fine tuning the default basically
permits most batch
applications to run without concern for the SIZE
parameter. The use of the
SIZE on the EXEC card should be a rare occurance.
The trick to to create a
snip .........



Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397



____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Randy Dray
20 years ago
Permalink
Thank you,

I will recommend that we remove the size parm from our
executions. Ive been a programmer for 5 years and
never seen a program go over 800. We have one in
development that is at 960. our default is set at
1280k.
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Jose Flores
20 years ago
Permalink
I have been using ,size=(auto,256k) and has worked well.

You need to remember that the left over partition after program is allocated
(getvis) is used by several other things, such as vsam?, 3rd party disk/tape
managers, and off-course, sort. Unless you plan on really fine tuning this
usage, allocating as much as you can for the partition will help.

I switch over from 4meg on vse 2.3.2 to 8meg on 2.5.2 for the batch
partitions and except for less than a handful, all has continued to work.


.---------------------------------------
. Jose L. Flores
. Arden Mayfair Inc.
. ***@gelsons.com
.---------------------------------------



-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf Of
Randy Dray
Sent: Thursday, July 28, 2005 9:31 AM
To: VSE Discussion List
Subject: RE: SIZE= parm on a cobol program exec

Thank you,

I will recommend that we remove the size parm from our
executions. Ive been a programmer for 5 years and
never seen a program go over 800. We have one in
development that is at 960. our default is set at
1280k.
...
Randy Dray
Business Systems Programmer
Morton Buildings Inc.

Morton IL

(309) 263-6397

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Tony Thigpen
20 years ago
Permalink
Just for grins, here is what z/VSE 3.1 sets up as a default when using
environment C:
ALLOC F1=32M
SIZE F1=1280K
ALLOC BG=32M
SIZE BG=1280K
ALLOC F2=256M
SIZE F2=2M
ALLOC F3=15M
SIZE F3=600K
ALLOC F4=32M
SIZE F4=2M
ALLOC F5=32M
SIZE F5=1M
ALLOC F6=32M
SIZE F6=1M
ALLOC F7=32M
SIZE F7=1M
ALLOC F8=512M
SIZE F8=2M
ALLOC F9=32M
SIZE F9=1M
ALLOC FA=32M
SIZE FA=1M
ALLOC FB=2M
SIZE FB=512K

Check out F2 at 256M. Remember, it's all virtual. :-)

Tony Thigpen


-----Original Message -----
From: Jose Flores
Sent: 07/28/2005 04:21 PM
...
Kevin Corkery
20 years ago
Permalink
They sort of seriously think you're going to run production in the ICCF
partition ;-)

Kevin P Corkery
Independent Consultant
Voorhees, New Jersey

-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU] On Behalf Of
Tony Thigpen
Sent: Thursday, July 28, 2005 5:57 PM
To: VSE Discussion List
Subject: Re: SIZE= parm on a cobol program exec


Just for grins, here is what z/VSE 3.1 sets up as a default when using
environment C:
ALLOC F1=32M
SIZE F1=1280K
ALLOC BG=32M
SIZE BG=1280K
ALLOC F2=256M
SIZE F2=2M
ALLOC F3=15M
SIZE F3=600K
ALLOC F4=32M
SIZE F4=2M
ALLOC F5=32M
SIZE F5=1M
ALLOC F6=32M
SIZE F6=1M
ALLOC F7=32M
SIZE F7=1M
ALLOC F8=512M
SIZE F8=2M
ALLOC F9=32M
SIZE F9=1M
ALLOC FA=32M
SIZE FA=1M
ALLOC FB=2M
SIZE FB=512K

Check out F2 at 256M. Remember, it's all virtual. :-)

Tony Thigpen
Tony Thigpen
20 years ago
Permalink
No, it's CICS/TS that uses a lot of storage. Even the 'smaller
environments' use around 100M for CICS.

Tony Thigpen


-----Original Message -----
From: Kevin Corkery
Sent: 07/28/2005 05:59 PM
...
Loading...