Re: Anyone need a random number generator?

------------------------------------<snip>-------------------------------

>  
>
>     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.
>
>
> Ok, I changed the JCL line to read SYS2.FORTLIB and it said that "**** 
> IRND now replaced in data set"
>
> 1) now how do I remove the old one from SYS1.FORTLIB ?

----------------------------<unsnip>--------------------------------------
To remove from SYS1.FORTLIB:

// job statement
//        EXEC  PGM=IEHPROGM
//SYSPRINT DD SYSOUT=A
//DISK  DD  DISP=SHR,UNIT=SYSDA,VOL=SER=  (The volume containing 
SYS1.FORTLIB )
//SYSIN DD *
 SCRATCH MEMBER=IRND,VOL=3330= (same volser),DSNAME=SYS1.FORTLIB
//

This assumes that the devtype is a 3330; replace with proper type as needed.

For safety's sake, ALWAYS put the member name FIRST in the control 
statements for this utility. A missing comma can lead to disastrous 
results if you change the order.

------------------------------------<snip>-------------------------------------

> 2) what do I do to use it in it's new place?

-------------------<unsnip>---------------------------------------------

In any LINKEDIT or LOADER step that refers to SYS1.FORTLIB
Replace:

//SYSLIB DD DSN=SYS1.FORTLIB,DISP=SHR

             With

//SYSLIB  DD  DSN=SYS1.FORTLIB,DISP=SHR
//               DD  DSN=SYS2.FORTLIB,DISP=SHR


This is called CONCATENATION of LIBRARIES and is quite a common practice 
in MVS, OS/360 and all the successor systems. The limit for this is 255 
total disk extents.

I don't object to off-list contact for this sort of thing.

Rick