¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

rabbit hole with MVS and pr3287


 

¿ªÔÆÌåÓý

(bcc: Paul Mattes so he can whack pr3287. "Paging Paul Mattes" ...)

I've got MVS 3.8 up at the TK3 UPD level humming. I have QUEUE and RPF updated and SPY working. (I don't have IMON yet). WATFIV is there. JRP is running (doing nothing), and I've migrated my personal files from my bastard system TK3.


Silly me, I got fancy and tweaked things ...

... and performance went completely to hell. Utterly. So bad I spent Saturday evening writing a SUBMIT EXEC to submit jobs from my 4361 VM test system to MVS because I couldn't stand the 4 seconds or worse just to close the editor under MVS.

I could not. tell. why.

I blamed shared spool, I blamed my cats, I blamed everything. So I simplified. I ripped things out, one by one. And finally, I found it.

What I had done is connect a 3287 printer for use with JRP via the command:

 pr3287 -reconnect -command cat -V PRT@hercules:3278

This was correct, but I had no PRT label on my 3287 devices in hercules.conf. x3270 bails on this problem with a no device available error, but it seems pr3287 trundles along and connects to any old device. Hercules and pr3287 do NOT play well after this.

(It was Hercules with the issue, not VTAM or JRP. Neither were shown to be taking CPU in QUEUE.)

After correcting the devices in hercules.conf and restarting ... the biblical performance issue went away.

-ahd-

p.s. VM TCP/IP RXSOCKET wonks, ping me offline for my RXSOCKET EXECs HOST, HOSTNAME, and SUBMIT.? If nothing else, they are test fodder for your VM/370 R6 implementation of RXSOCKET.

-- 
Drew Derbyshire

"We haven't been properly introduced. I'm Buffy, and you're history."
                                    -- "Buffy the Vampire Slayer"


 

Thanks for the story; that will be helpful to some poor sod in the future.

I have found that adding SYSCPK to TK3UPD is one of the easiest ways to get the extra compilers, rather than adding them one by one. There are plenty of 3350 addresses in TK3UPD...

No IMON: not present, or not working? I don't recall have to fiddle with it (except possibly adding a PROC so I can start it from the console w/ a dedicated terminal, bypassing TSO, but even that may have already been done).