IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

FIXED BIN (31) and FIXED BIN (63) - How many bytes?


IBM Mainframe Forums -> PL/I & Assembler
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sundarkudos

New User


Joined: 16 Oct 2008
Posts: 39
Location: Chennai

PostPosted: Thu Nov 05, 2015 1:11 pm
Reply with quote

Dear All,

Currently, we are working on migrating PL/I v1.1 code to Enterprise PL/I v4.2.

In some programs, variables are declared as FIXED BIN(63) where the below warning is encountered while compiling with PL/I v4.2 but no warning with Pl/I v1.1.

IBM1151I W FIXED BINARY precision is reduced to maximum value(31).

Explanation: The maximum FIXED BIN precision depends on the LIMITS
option.

Hence, declared variable will be reduced to FIXED BIN(31).

I hope the same truncation/reduction would have happened with v1.1 also, though it did not throw any warnings. So, I'm not providing any fix for this warning, as the functionality would remain unaltered.

Just wanted to get experts opinion also. Please share your thoughts.

Thanks,
Sundar.
Back to top
View user's profile Send private message
prino
Warnings : 1

Senior Member


Joined: 07 Feb 2009
Posts: 1238
Location: Vilnius, Lithuania

PostPosted: Thu Nov 05, 2015 1:29 pm
Reply with quote

sundarkudos wrote:
I hope the same truncation/reduction would have happened with v1.1 also, though it did not throw any warnings. So, I'm not providing any fix for this warning, as the functionality would remain unaltered.


Idiot! If the compiler gives you a warning, you DO something about it.

"Oh, I've got black ever growing mole on my arm, but it doesn't hurt, so I'll leave it as I can still move my arm"

Types of you are a cancer on our profession!

DID YOU EVER BOTHER TO READ THE EFFING MANUAL AND WHAT THE LIMITS OPTION IS FOR?
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7311
Location: Inside the Matrix

PostPosted: Thu Nov 05, 2015 1:44 pm
Reply with quote

You need all the compiler options the same between the two releases, or to know exactly the impact of any differences.

You can't make any assumptions like you have made. They don't make sense.
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2504
Location: Atlanta, Georgia, USA

PostPosted: Thu Nov 05, 2015 5:35 pm
Reply with quote

FIXED BIN (31) is S9(08) BINARY in COBOL

FIXED BIN (63) is S9(18) BINARY in COBOL.

This should get you on your way.

In the future, please refer to the manuals. Not only for yourself, but for the rest of us. icon_wink.gif
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2448
Location: Hampshire, UK

PostPosted: Thu Nov 05, 2015 7:33 pm
Reply with quote

Well it wouldn't throw a warning as nothing on the mainframe throws anything - except, perhaps, an operator!

Also FIXED BIN(31) is 31 bits + 1 sign bit - therefore 32 bits. I leave the conversion to bytes to you.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> PL/I & Assembler

 


Similar Topics
Topic Forum Replies
No new posts comparasion between BIN FIXED(63) an... PL/I & Assembler 10
No new posts Variable length(Pipe delimter) to Fix... DFSORT/ICETOOL 8
No new posts ICE039A H INSUFFICIENT MAIN STORAGE -... DFSORT/ICETOOL 3
No new posts converting bytes and megabytes to kil... SYNCSORT 4
No new posts from CSV to fixed DFSORT/ICETOOL 7
Search our Forums:

Back to Top