DEFINE EVENT,ID=AUTOFTP,TYPE=POWER,CLASS=S,QUEUE=LST,ACTION=FTP
DEFINE EVENT,ID=SMETFTP,TYPE=POWER,CLASS=T,QUEUE=LST,ACTION=FTP
If I had already had some listings in the LST queue with CLASS=S, autoftp
will start as normal with
scripts defined.
If I had a couple of reports generated during the autoftp of CLASS S
listings they will have to wait
until no more listings of CLASS=S is in the LST queue before they are
downloaded
Is there a way that I can change the priority of those listings with
CLASS=T to jump the queue
after the current report of CLASS=S is completed downloaded, to be the next
in line for autoftp ??
Also sometimes the AUTOFTP event "hangs" and I need to shutdown TCP/IP and
restart again.
Is there a way to only shutdown the DEFINE EVENT for autoftp and re-DEFINE
again on the console
without impact on those already signed on thru TELNET applications to log
off ?
All help appreciated
Thanks
Mr. Cheah Hin Weng
Sr. Asst Manager
Info Tech Center
Sony Electronics(M) Sdn Bhd
Prai Free Trade Zone
Butterworth, Penang, Malaysia
Tel: 604-3901304
Fax: 604-3991620
> Also sometimes the AUTOFTP event "hangs" and I need to shutdown TCP/IP and
> restart again.
> Is there a way to only shutdown the DEFINE EVENT for autoftp and re-DEFINE
> again on the console
> without impact on those already signed on thru TELNET applications to log
> off ?
>
As of service pack I, I could not find any documented DELETE EVENT command
for TCP/IP for VSE 1.3. Therefore, you may want to consider setting up a
second TCP partition to handle your FTP needs and have this partition
communicate with the original TCP partition using the supported
cross-partition communication facility. With proper routing statements,
you can have all the TCP traffic flow through a single hardware adapter to
the original TCP where traffic addressed to the second (FTP) TCP is sent
to it over the cross-partition link. With this approach, your TN3270
sessions are not affected by the need to shut down and restart the FTP
TCP.
If you are interested in this approach, a few points to keep in mind in
setting up the configuration are
- Each TCP partition has to have a unique IP address.
- The primary TCP partition (the one that owns the hardware
adapter) must be defined with
GATEWAY ON
and
DEFINE ALTIP,ID=TCP2,IPADDR=IP address of second partition.
- The primary TCP partition must contain a route statement that directs
traffic destined for the secondary partition through the cross-partition
link
DEFINE ROUTE,ID=TCP2,LINKID=TCP_2_TCP, -
IPADDR=IP address of secondary
- The secondary TCP partition must contain a route statement that points
all traffic back through the primary
DEFINE ROUTE,ID=EVERYTHING,LINKID=TCP_2_TCP,IPADDR=0.0.0.0, -
GATEWAY=IP address of primary
- Each TCP partition must contain a definition for the cross-partition
link
DEFINE LINK,ID=TCP_2_TCP,TYPE=IPNET,SYSID=01 (primary)
DEFINE LINK,ID=TCP_2_TCP,TYPE=IPNET,SYSID=00 (secondary)
> Thanks
> Mr. Cheah Hin Weng
> Sr. Asst Manager
> Info Tech Center
> Sony Electronics(M) Sdn Bhd
Bob Jacobson
Delta Dental Plan of Minnesota
(651) 994-5329
rjac...@deltadental.org