Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2258

March 9th, 2012 09:00

How do I use the IVP under z/OS?

I have downloaded and installed the latest z/OS SDK (V3R1M544) and I am trying to run the IVP against the EMC Public clusters.  I have tried specifying the PEA (c1profile1.pea) file a number of different ways and none of them seem to work.  I get a FP_NO_POOL_ERR from FPPool_Open().  The closest I have come is by specifying:  168.159.214.19?DD:PEA  but without the PEA DD name specified.  This at least gave me an authentication error.

I am mainly trying to get the synatx 'right' in my program and thought this would give me a clue.

Thanks!

Mark

10 Posts

March 14th, 2012 14:00

All,

Thanks for your help.  After talking to my Systems Programming group again (first person wasn't aware), it turns out there is a problem with the TCP/IP stack on our primary z/OS image.  Running on an alternate image worked just fine (using the latest PEA file, thanks again for the information Dan).

Just FYI, 168.159.19?//'MY.PEAFILE' worked as did 168.159.19?'MY.PEAFILE' (no slashes).  Specifying  CENTERA_PEA_LOCATION='MY.PEAFILE' in FPCONFIG worked correctly as well.

Cheers!

Mark

10 Posts

March 13th, 2012 14:00

More information for anyone interested:

If I specify the 'centera_address' as '168.159.214.19?port=3218' I wind up with:

IVPTEST : Error -10153 from FPPool_Open()

              : FP_AUTHENTICATION_FAILED_ERR

              : Failed to authenticate PEA data

The question becomes, why do I have to specify the port if the 'default' port is 3218?

Also, how do you specify the PEA file?  If I specify 'centera_address' as "168.159.214.19?port=3218,pea_file_name" (where pea_file_name is the z/OS dataset name), I get the same error mentioned above with the following:

               :   .        (168.159.214.19?port=3218,pea_file_name,PAIRef)

::Open(168.159.214.19?port=3218,pea_file_name)<_FPPool_Open(168.159.214.19?port=3218,pea_file_name)

l_Open(168.159.214.19?port=3218,pea_file_name)

I then tried "168.159.214.19?port=3218,PAIRef=pea_file_name" with the same results (sans the PAIRef highlighted above).

This is using either c1profile1.pea or c1armtestint.pea (after FTPing to z/OS).

I even tried setting CENTERA_PEA_LOCATION in the FPCONFIG DD and get the same results.

HELP!!!

Mark

41 Posts

March 14th, 2012 01:00

You shouldn't specify the port. When you specify '168.159.214.19?port=3218' the SDK probably takes 'port=3218' as the name of the pea file or something, and authentication fails.

Maybe try first with JCasScript (or CenteraPing) to make sure you can actually connect to the Centera, and then try with your own application.

You already menationed that you tried to connect with various connection strings. Which combinations did you try already?

Regards,

Kim Marivoet

10 Posts

March 14th, 2012 07:00

I used CenteraPing and Centera Viewer from my PC and was able to connect just fine.  However, neither of those run under z/OS so I am am trying to use the EMC supplied IVPTEST program as a kind of 'CenteraPing' analog.

Some of the connection strings I have tried:

168.159.214.19 -- returns 'FP_NO_POOL_ERR', this is with CENTERA_PEA_LOCATION specified in the FPCONFIG DD

168.159.214.19:3218 -- same result

168.159.214.19,port=3218 -- same result

168.159.214.19?name= ,secret= -- same result

168.159.214.19?pea_file_name -- same result

168.159.214.19?pea_file_name,port=3218 --same result

As mentioned earlier, if I put port=3218 immediately after the question mark, I get a FP_AUTHENTICATION_FAILED_ERR.

Thanks for your interest.

Mark

41 Posts

March 14th, 2012 08:00

It seems that the cluster you're trying to connect to is not reachable from the machine that is running the IPVTEST program. Is it possible that this machine is on a different network for example, or that there is some firewall configuration that would block the connection to the Centera from this machine?

Regards,

Kim

5 Practitioner

 • 

274.2K Posts

March 14th, 2012 09:00

Mark,

You need to ensure that mainframe peafile is Sequential datset with RECFM=VB and LRECL=27920  ... yes these are strange attributes.

and you need single quotes around dataset

connection string

168.159.214.19?//'MY.PEAFILE'

-Dan

10 Posts

March 14th, 2012 12:00

Kim,

I tried a different "port=" value and got the same authentication error so you may be right about it thinking it is the pea file.  However, I wonder why it is not accepting the CENTERA_PEA_LOCATION in the FPCONFIG DD (program is straight out of the C libaray without any changes)?  The documentation says it should use that if the pea file is not specified in the connection string.

Thanks for you help!

Dan,

Thanks for the info about the file format.  I had tried both a sequential and PDS but not with that LRECL.  Should the file be one long record?  I took the one off of the website, changed the end-of-line convention to be 'windows' and FTP'd it to the mainframe in ASCII mode.  I also tried to send it binary but not with that dataset format (so don't know how that will work).  I have now tried "168.159.214.19?pea_file_name" and "168.159.214.19?'pea_file_name'" with no luck (still get FP_NO_POOL_ERR).  I have tried specifying the '//' as well, but the C++ runtime intercepts that and drops off the IP address (if it wasn't clear before, the parameters are passed to the IVP via PARM= on the execute statement).

Thanks for the suggestions!

Mark

5 Practitioner

 • 

274.2K Posts

March 14th, 2012 12:00

Mark,

You should NOT edit the peafile at all (no need to touch or add any CR/LF chars in peafile)… you ftp it "binary" to mainframe to a mainframe seq dsn with the dcb attributes already detailed. The mainframe side reads the peafile as ASCII

I will work on the question about CENTERA_PEA_LOCATION overnight and get an answer tomorrow morning

-Dan

10 Posts

March 14th, 2012 13:00

Dan, I created a copy of IVPTEST and changed it to:

rCentera = FPPool_Open("168.159.214.19?//'MY.PEAFILE'");

Where 'MY.PEAFILE' is a VB LRECL=27920 flatfile with the c1profile1.pea file FTP'd into it as binary.  Still get the FP_NO_POOL_ERR.

On the flip side, it does appear to be opening the file even from the CENTERA_PEA_LOCATION.  If I specify a valid file name (i.e. MY.PEAFILE), then I get the FP_NO_POOL_ERR.  If I specify a bogus file name (i.e. NOT.A.FILE), I get the FP_AUTHENTICATION_FAILED_ERR (which seems to indicate that fopen() didn't work rather than, as I had assumed, the Centera didn't like the credentials).

Thanks again!

Mark

No Events found!

Top