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

Charles,

I'm not familiar with GENTRAN, but try this...

rename the original *cmd object STRCMNSSN or move it to another library
create a duplicate object of that command back to it's origional library,
with the original name.
change that command to run a CL program of your choosing instead of what it
would normally do.
write this CLP to send a message or whatever would help simulate the
STRCMNSSN.
document what you've done, so that you can re-do it if you ever replace the
library (upgrade?)

if you actually need to run the real STRCMNSSN on occasion, run the renamed
command.

hth,

Rick

--------original message----------
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?