RE: Anyone need a random number generator?
"John R. Macdonald" <[email protected]>
| Newsgroups | gmane.comp.emulators.turnkey-mvs |
|---|---|
| Organization | Home |
| Message-ID | <22DB6684E0844D39A93B891FFFB5F703@JohnPC> |
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rick Fochtman Sent: jeudi 29 avril 2010 20:19 To: [email protected] Subject: Re: [turnkey-mvs] Anyone need a random number generator? ------------------------------<snip>--------------------------------------- On Wed, Apr 28, 2010 at 12:39 PM, Rick Fochtman <rfochtman@ync. <mailto:[email protected]> net> wrote: //SYSLMOD DD DSN=SYS1,FORTLIB(IRND),DISP=SHR <-- member name is LMOD name when link is complete -----------------------------------------------------------^^^^^ Rick <mailto:[email protected]?subject=Anyone%20need%20a%20random%20number%20ge nerator?> <mailto:[email protected]?subject=Anyone%20need%20a%20random%20num ber%20generator?> <http://groups.yahoo.com/group/turnkey-mvs/post;_ylc=X3oDMTJwYjNyZWxhBF9TAzk 3MzU5NzE0BGdycElkAzgxNjExNjIEZ3Jwc3BJZAMxNzA1MDA2NTU5BG1zZ0lkAzY1MzQEc2VjA2Z 0cgRzbGsDcnBseQRzdGltZQMxMjcyNDcyNDYz?act=reply&messageNum=6534> If I wanted to add other subroutines or functions to the source code would that be ok too? or should I duplicate this whole file and change names? ---------------------------------<unsnip>------------------------------ You might want to build a separate library for your additions; in my own way of thinking, I'd call it "SYS2.FORTLIB" and add it to the SYSLIB concatenation in any LINKEDIT or LOADER steps in my FORTRAN procs. That might be helpful in separating your routines from the IBM-supplied library. Rick Ron In addition to building a separate library for your user stuff IMHO you would be better off by having a separate module for each subroutine or function you require. Puting it all in one module will : - limit you to a maximum of 16 functions (1 main entry point + 15 aliases for the secondary EPs IIRC) per module (which also means that if you write more than 16 routines you'll have to remember in which module a particular function is) - increase the size of the final load module beyond what is really necessary - increase the size and complexity of the source code - introduce the possibility of accidentally clobbering perfectly good code in function B while adding/modifying function C then spend hours trying to figure out what happened - in the same vein introduce subtle side effects between two or more functions I haven't coded in FORTRAN so I don't how easy/difficult it is to code secondary entry points for this FORTRAN compiler (I have done it in COBOL & PL/I though, which is how I found out about the 16 EPs limitation) HTH John