I would guess the default queue for ftp (incoming from outside) would be
the queue that the JINETD job started in.
From a session or a job I would think it would be CS and DS. (Presuming
that's what your defaults are.)
Can be overridden by ;PRI= on the job card.
(Notice I still call it a card?)
On 12/15/22 10:56, James B. Byrne wrote:
> Thu, December 15, 2022 09:40, Craig Lalley wrote:
>> Jame,
>> Have you tried passive?
>> Type “passive†after typing “binaryâ€
>> -CraigÂ
>>
> Passive ftp gives the same result:
>
> ftp> get ./STDHAL.1.1 ./STDHAL.1.1;CODE=STORE;REC=-256,,F,BINARY
> 227 Entering Passive Mode (192,168,216,37,80,84).
> 150 Opening BINARY mode data connection for ./STDHAL.1.1 (717089024 bytes).
> Data Transfer Request Failed. (FTPERR 13)
> 226 Transfer complete.
> 221 Goodbye.
>
> However, if I connect from a terminal session then the ftp transfer completes.
>
> What are the default priority queues for interactive sessions and batch jobs
> respectively? CS and DS? Would this be a possible factor? How can one
> discover what priority queue a session or job is running in?
>
> I do not think that I have looked into this sort of stuff in over 20 years.
>
>
>
--
Tracy Johnson
BT
NNNN
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|