RE: Code V5R1M0 doesn't report events back after Win2k upgrade

Buck Calabro <[email protected]>
Newsgroups gmane.comp.systems.as400.code
Message-ID <A1767D18AF09D511B99A00508B55A9FA014B3073@commsoft-exchg.commsoft.net>
>try STRCODE with *RESOLVE on your iSeries again 
>to see if it helps;


STRCODE SERVER(AS400COM) RMTLOCNAME(*RESOLVE)

No good.  If I don't specify the port, I get the following message:
Message ID . . . . . . :   EVF4001       
Message . . . . :   The port number specified is not correct.

Cause . . . . . :   The port value specified was 00.



STRCODE SERVER(AS400COM) RMTLOCNAME(*RESOLVE) PORT(4200)  

When I specify port 4200, I get an error window with the following:
Handshake information from the host server contains errors.
Connection request from 'COMMSOFT' has been ended by the daemon.

The unusual thing about this is that the iSeries I am running this from is
called AS400COM.


>DUMPOBJ STRCODE *USRSPC to SPL and check if the 
>IP address is correct for your workstation.

I did, and it was.  Just for grins, I deleted the user space and let STRCODE
re-create it.  No luck.

>Make sure that you apply TWEAK if you want the 
>completion message to be popped up.

Thanks, but there's no message to pop up; nothing to change focus to.
Thanks for trying Hak!  I appreciate it!
  --buck
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.