Retrieving RPF V1R9M0 (and later) and Installing

Beginning with V1R9M0, Rob Prins is distributing RPF in XMIT archives, rather than the AWS tape image, which he used for previous releases.  These are the steps necessary to retrieve the XMIT archives from Rob Prins' website and installing under MVS 3.8j.

There are seven archives available for download from Rob Prin's website [http://www.prince-webdesign.nl/index.php/software/].  Because RPF is distributed for use on both z/OS and MVS 3.8j, one of those archives is totally unnecessary for installation on MVS 3.8j, leaving the six relevant archives as:

• File 1. rpf190mv.zip, the MVS38J and MVS380 load modules.
• File 3. rpf190he.zip, the RPF HELP library.
• File 4. rpf190jc.zip, the RPF JCL library.
• File 5. rpf190as.zip, the RPF source library.
• File 6. rpf190pn.zip, the RPF ISPF panel library.
• File 7. rpf190s1.zip, the RPF macro library (for MVS38J and MVS380 only).

In order to utilize RPF under TSO, it is only necessary to retrieve/install Files 1, 3, and 4.  If you want to use RPF under Wally McLaughlin's ISPF, you will also need File 6.  Files 5 and 7 are necessary if you want to re-assemble the source.

Retrieve/Upload to MVS 3.8j

Although you may not choose to install all six of the archive on your MVS 3.8j system, I will include the instructions, and jobstreams, for all of them below.

First you should download the zip archives from http://www.prince-webdesign.nl/index.php/software/ (scroll down until you see the heading Current Releases).  Unpack each of the archives you download; each with contain a single XMIT format archive with similar naming convention as the zip archive: 

• rpf190mv.zip contains rpf190mv.xmi
• rpf190he.zip contains rpf190he.xmi
• rpf190jc.zip contains rpf190jc.xmi
• rpf190as.zip contains rpf190as.xmi
• rpf190pn.zip contains rpf190pn.xmi
• rpf190s1.zip contains rpf190s1.xmi

I would suggest placing the xmi files in the JCL directory under MVS, which is consistent with my MVS 3.8j installation instructions.

I loaded the Partitioned Datasets from the archives into datasets on my MVS 3.8j system with a high level qualifier of RPF.  If you follow this naming convention and you do not already have a VSAM alias defined on your system of RPF, you will need to define the alias, which is easily done at a TSO prompt:

You will need to supply the password for the Master Catalog, which on my system, and probably on any system built using my instructions, is SYSPROG.  The profile noprefix command is required before issuing the define alias command; if you use a prefix with TSO, you will need to re-establish the prefix with the profile prefix(prefix value) after issuing the define alias command.

Next, for each of the archives, you will need to submit a job to use the program RECV370 to transfer the XMIT file to MVS and unpack it.  There is a prototype job in SYSC.JCLLIB(RECV370) that may be quickly tailored to the needed requirements.  

RPF Load Modules

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.LOADLIB, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(1,0,10),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190mv.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190mv.pdf.

RPF Help Text

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.HELP, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(1,0,10),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190he.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190he.pdf.

RPF Jobstreams

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.JCL, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(1,0,10),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190jc.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190jc.pdf.

RPF Assembly Source Code

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.SOURCE, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(10,0,15),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190as.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190as.pdf.

RPF Assembly Macros

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.MACLIB, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(5,0,10),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190s1.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190s1.pdf.

RPF ISPF Panels

Here is the tailored JCL for the job:

//RECV370 JOB (1),'UNPACK XMIT',CLASS=A,MSGCLASS=X //*-------------------------------------------------------- //RECV1 EXEC RECV370 //XMITIN DD UNIT=01C,DCB=BLKSIZE=80 <- INPUT //SYSUT2 DD DSN=RPF.R190.PANELS, <- OUTPUT // VOL=SER=PUB000,UNIT=SYSDA, // SPACE=(CYL,(5,0,10),RLSE), // DISP=(,CATLG)

In the JCL above, the input dataset (XMITIN DD statement), you are specifying the exact address of a card reader that is emulated by Hercules.  On the Hercules command window, initialize the card reader to point to the file on your host Operating System that holds the XMIT to be transferred.  The Hercules command is devinit 01c <path>/rpf190pn.xmit ebcdic.  You should specify the correct path to the file in place of <path> in the example command.  Note:  The command shown here in red specifies address x'01c' which is the correct address for an MVS system built using my instructions.  The address specified must match a device in your MVS system that is defined as a card reader and that card reader must not be managed by JES2.  It is also imperative that you include the ebcdic operand to inform Hercules to not do ASCII to EBCDIC translation when the host Operating System file is read in.

The output dataset may be named whatever meets your MVS 3.8j system requirements.  On my system, there is already an alias for RPF that directs cataloging in User Catalog UCPUB000, which is appropriate as I am loading the dataset onto volume PUB000.

Submit the job to MVS to transfer the XMIT dataset to MVS and unpack it.  The output for this job may be viewed at rpf190pn.pdf.

Copy Load Modules

In the RPF Jobstreams Partitioned Dataset [RPF.R190.JCL] there is a job [$CMDLIB] which you will use to copy the RPF load modules to your TSO Command Library, probably it is called SYS2.CMDLIB on your system.  I made a few changes, since the name where I installed the contents of the archive was different from what $CMDLIB is distributed to use and also changed the NOTIFY parameter on the JOB card.

Submit the job to MVS to copy the RPF load modules to the library where TSO loads modules from.  The output for this job may be viewed at $cmdlib.pdf.

Copy Help Text

In the RPF Jobstreams Partitioned Dataset [RPF.R190.JCL] there is a job [$COPYHLP] which you will use to copy the RPF help text members to your TSO Help Library, probably it is called SYS2.HELP on your system.  I made a few changes, since the name where I installed the contents of the archive was different from what $CMDLIB is distributed to use and also changed the JOB card parameters to suit me.

Submit the job to MVS to copy the RPF help text members to the library where TSO loads help text from.  The output for this job may be viewed at $copyhlp.pdf.

Create RPF Profile

If you are installing RPF for the first time, you need to create the VSAM profile cluster.

In the RPF Jobstreams Partitioned Dataset [RPF.R190.JCL] there is a job [$PROFILE] which will define and load the initial seed record to the RPF Profile cluster.  You will need to change the Volume Serial number for where the dataset will reside and remove the comments about tailoring the jobstream (the comments will cause an error in IDCAMS).  I also changed the JOB card parameters to suit me.

Submit the job to MVS to define and load the RPF Profile dataset.  The output for this job may be viewed at $profile.pdf.

Add RPFPROF DD to TSO Procedure

You will need to edit the catalogued procedure that is used when a TSO user logs on, probably SYS1.PROCLIB(IKJACCNT), to add the DD statement for the RPF Profile Dataset:

//RPFPROF DD DISP=SHR,DSN=RPF.PROFILE. 

After saving the changes, log off and back on. RPF should now load at the TSO prompt:

I hope that you have found my instructions useful.  If you have questions that I can answer to help expand upon my explanations and examples shown here, please don't hesitate to send them to me:

Return to Site Home Page Frequently Asked Questions

This page was last updated on June 26, 2022 .