× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2004

GENTRAN EDI and developing on a separate box: How to prevent comm unications?

All,

Anyone have any experience preventing communications from GENTRAN on a
development box.

What I'm looking for is a "Simulate Comms" setting.  We want our CL's to be
able to have the STRCMNSSN command in them, but not actually do anything.
At the same time, it should act as if a comms setting was successful since
the program check the comm history file for success.

Possible solutions

1) Change all comms scripts to not do anything (profiles too?)

2) add "if system *NE test then" around the strcomssn (and the check for
success?)


Anybody have better ideas or experience with this?


Thanks,
Charles

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.