|
View previous topic :: View next topic
|
| Author |
Message |
chandramouliravi
New User
Joined: 27 Apr 2009
Posts: 26
Location: addison
|
|
|
|
Hi,
When i use
| Code: |
| $ORTPARM : BMSG,VSCORE=15K |
,
i get below B messages. As i undestand, there is max of 8196K available below 16M and 7,936K available above 16M.
Which space does SYNCSORT prefer first among 8196K and 7,936K.
Please clarify.
| Code: |
SYNCSORT FOR Z/OS 1.3.0.2R
WER164B 8,196K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX
REQUESTED,
WER164B 0 BYTES RESERVE REQUESTED, 272K BYTES USED
WER410B 7,936K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,
WER410B 0 BYTES RESERVE REQUESTED, 156K BYTES USED |
|
|
| Back to top |
|
 |
krisprems
Active Member
Joined: 27 Nov 2006
Posts: 649
Location: India
|
|
|
|
Yes, ur understanding seems to be correct, however here is the explanation of the message codes:
| Quote: |
WER410B XXX BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE
16MEG LINE,
YYY BYTES RESERVE REQUESTED, ZZZ BYTES USED
EXPLANATION: The amount of virtual storage
above the 16-megabyte line available (free)
when SyncSort received control is represented
by x's. The amount of virtual storage that the
user requested SyncSort to reserve above the
16-megabyte line is represented by y's. The
amount of virtual storage used by SyncSort
above the 16-megabyte line is represented by
z's. |
| Quote: |
WER164B WWW BYTES OF VIRTUAL STORAGE AVAILABLE, XXX
BYTES REQUESTED, YYY BYTES RESERVE REQUESTED,
ZZZ BYTES USED
EXPLANATION: The amount of virtual storage
available (free) when SyncSort received control
is represented by w's. The amount of virtual
storage requested for SyncSort's use is repres-
ented by x's. The amount of virtual storage
that the user requested SyncSort to reserve be-
low the 16-megabyte line is represented by y's.
The amount of virtual storage used by SyncSort
is represented by z's. For XA systems, this
message reflects the total amount of virtual
storage below and above the 16-megabyte line
thas was available to SyncSort and used by
SyncSort.
|
| Quote: |
WER410B XXX BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE
16MEG LINE,
YYY BYTES RESERVE REQUESTED, ZZZ BYTES USED
EXPLANATION: The amount of virtual storage
above the 16-megabyte line available (free)
when SyncSort received control is represented
by x's. The amount of virtual storage that the
user requested SyncSort to reserve above the
16-megabyte line is represented by y's. The
amount of virtual storage used by SyncSort
above the 16-megabyte line is represented by
z's. |
|
|
| Back to top |
|
|
chandramouliravi
New User
Joined: 27 Apr 2009
Posts: 26
Location: addison
|
|
|
|
Hi krisprems,
Why is Syncsort having separate space aboeve and below 16M.
Why cant it have a single storage. I dont understand what is significance 16M?
Thanks,
Chandra mouli |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
On the mainframe, storage can be allocated either above or below "the line".
"The line" means the point at which memory addresses require four bytes of storage to hold them rather than three bytes - that is, addresses above 16Mb. The mainframe is limited to 31-bit addressing, but pointer variables are always 32 bits long and the unused bits are available for use by user programs. The format of these pointer variables on the mainframe is different to that native to the Intel PC platform. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
On the other hand, a message of tyoe B (and C, D & I) are informational messages, so you should not be worried.
'B' messages are helpful in tuning specific applications. Some times they are not enabled as an installation default, then BMSG can be specified as a runtime parameter... and this is evident from what Krisprems has posted. |
|
| Back to top |
|
|
chandramouliravi
New User
Joined: 27 Apr 2009
Posts: 26
Location: addison
|
|
|
|
post edited to remove improper content...
requesting private communications
posting an eMail address
for private communications use the forum PM facility |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
Chapter 3 of "Principles of Operation" will give all info on
addresses. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
| The mainframe is limited to 31-bit addressing, but pointer variables are always 32 bits long and the unused bits are available for use by user programs. |
And what about AMODE(64) - addresses above the 'bar' where pointers are 64bits ? The reason for 31-bit addressing rather than 32 bit was for compatibility reasons. The "unused" bit is used in the PSW to indicate the current AMODE. When moving to AMODE(64), the low-order bit is used to indicate AMODE.
If the low-order bit is 'on' the program is running AMODE(64) and all other bits in the PSW are part of the address. If the low-order bit is 'off' the program may be running in AMODE(31) or AMODE(24), depending on the setting of the high-order bit. If the high-order bit is 'on', the program is running in AMODE(31) whereas if it is 'off' the program is running in AMODE(24).
Garry. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Thanks Garry - I completely missed that 64-bit thing...  . Was reading and I could read to chapters which explains about 31-bit things by the time i replied in... |
|
| Back to top |
|
|
|
|
