Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1008
  • Last Modified:

CAnnot get SNDTCPSPLF to work from V5R3 to V5r1

When trying to send spooled files from one box runing V5R3 to another using V5R1, I get error msg cannot connect to remote system 128.200.0.1. Even though it works the other way around. Is sndTCPsplf backwardsly compatable?

Regards
James
0
ulsterweavers
Asked:
ulsterweavers
  • 3
  • 3
  • 2
  • +1
7 Solutions
 
_b_hCommented:
There should be no issue sending back to v5r1; I just tested it on my v5r3 and v5r1 systems. It could be the IP config.
Can you ping and telnet to the v5r1 system?
Please post the exact message that you are getting.

Barry
0
 
tliottaCommented:
AFAIK, Barry's right. There should be no issue with SNDTCPSPLF that relates to V5R1 vs. V5R3. The problem is in the relative TCP/IP configurations or somewhere along the route.

(Note that this also assumes that TCP/IP PTFs, etc., are in place. Obviously, if something's "broken"...?)

Tom
0
 
ulsterweaversAuthor Commented:
Hi Barry, Tom,
I can telnet and ping in both directions:I get the following error msg when trying SNDTCPSPLF:
 Message ID . . . . . . :   TCP3427       Severity . . . . . . . :   10        
 Message type . . . . . :   Diagnostic                                          
 Date sent  . . . . . . :   12/06/08      Time sent  . . . . . . :   08:29:07  
                                                                               
 Message . . . . :   Remote host system rejected the open attempt.              
 Cause . . . . . :   This may have occurred because the remote host does not    
   have ports available for use or does not support TELNET.                    
 Recovery  . . . :   Try the request again or contact the system administrator.

When I set up a remote queue (which is the main reason why I'm doing this) I get the following msg:
Message ID . . . . . . :   TCP2617       Severity . . . . . . . :   20      
Message type . . . . . :   Diagnostic                                      
Date sent  . . . . . . :   11/06/08      Time sent  . . . . . . :   17:10:48
                                                                           
Message . . . . :   TCP/IP connection to remote system 128.200.0.31 closed,
  reason code 3.                                                            
Cause . . . . . :   The TCP/IP connection to remote system 128.200.0.31 has
  been closed. The connection was closed for reason code 3.  Full connection
  details for the closed connection include:                                
    - local IP address is 128.200.94.4                                      
    - local port is 23                                                      
    - remote IP address is 128.200.0.31                                    
    - remote port is 1175                                                  

I have went through all the tcp settings in the boxes and can see no differences at all. Any ideas?

James
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
MurpheyApplication ConsultantCommented:
Hi ulsterweavers,

I know that there are some backwards compatibility problems if the OS difer more then 1 release,
(That's why we avoid that within our company.)

But as far as I can remember, OS/400 was always 100% upwards compatible, so I would expect  that you at least should be able to send from V5R1 to  V5R3.

Regards,
Murph
0
 
ulsterweaversAuthor Commented:
Yes, I can send from V5R1 to V5R3. Just not the other way.

James
0
 
_b_hCommented:
I tested a remote outq from v5r3 to v5r1 to confirm that it does work.

I am not sure what parameters were used to create the outq, but check out these:
CRTOUTQ OUTQ(MYLIB/MYOUTQ)        
        RMTSYS(*INTNETADR)          
        RMTPRTQ('QGPL/QPRINT')      
        AUTOSTRWTR(1)              
        CNNTYPE(*IP)                
        TRANSFORM(*NO)              
        INTNETADR('<ipaddress')  

Post back!
Barry
0
 
ulsterweaversAuthor Commented:
Hi Barry,

Yes, thats what I used, but it doesn't work... cannot see whats up with it at all.
Its driving me nuts!

James
0
 
_b_hCommented:
Double-check that the outq has the correct IP address (sorry, have to ask)
Verify that the LPD server has been started on v5r1 box
Barry
0
 
MurpheyApplication ConsultantCommented:
Hi James,
      
sorry for the "hi Hi ulsterweavers" :)

"Yes, I can send from V5R1 to V5R3. Just not the other way."

I'm affraid that this is one example of the incompatibility of 2 releases.

In this case, I think there are 2 options left.
- Upgrade to V5R2  (at least), what is the best solution but sometimes  for some reason hard to do
- Copy the spoolfile to a PF send it to your other system and create a new spoolfile (see Snippet)
 
Regards,
Murph
/* Create a example spool e.g. */
dspsyssts output(*print) 
 
/* Copy file to PF MyFile in MyLib*/
CPYSPLF FILE(QPDSPSTS) TOFILE(MyLib/MyFile) SPLNBR(*LAST) CTLCHAR(*FCFC) 
 
NOW: Get this file to the other system with ftp or whatever.
 
to get the file back as spoolfile
 
/* Prepare new destination for spoolfile */
OVRPRTF FILE(NEWSPLF) TOFILE(QPRINT)
PAGESIZE(66 132) LPI(6) OVRFLW(60) CTLCHAR(*FCFC)
PRTTXT('My Spool from other system')
 
/* Copy file to the Overridden file */
CPYF MyLib/MyFile NEWSPLF 
 
/* Done :) */

Open in new window

0
 
tliottaCommented:
Minor note... "Remote host system rejected the open attempt." That says that the LPR/LPD server hasn't been started on the remote system. Use STRTCPSVR *LPD command on the remote system to get it started.

I see that Barry has already mentioned this, but I don't see a response yet.

If the server app isn't running, version differences will be irrelevant.

Tom
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now