I'd recommend nothing less than 32M these days for a user v-machine.
Memory is cheap. (And bandwidth is cheaper, to repeat an olde quote.)
Seriously, while you might justifiably want to constrain some service
machines, let the users have more. No telling what they might
legitimately need to do. See if you are already allowed:
def stor 16m
ipl cms
and then retry the ftp.
-- R;
On 2010-07-03, Paul Gilmartin <[email protected]> wrote:
> On Jul 3, 2010, at 03:43, John Hartmann wrote:
>
>> The regression test now ensures that all abbreviations resolve and
>> this test is independent of generating the table.
>>
> Trying to fetch this, I get:
>
> cd academ:pipeline.eweb
>
>>>>CWD academ:pipeline.eweb
>>>>
> 250 SFS working directory is ACADEM:PIPELINE.EWEB
>
> Command:
>
> dir
>
>>>>PORT 10,80,63,52,248,220
>>>>
> 200 Port request OK.
>
>>>>LIST
>>>>
> 125 List started OK
>
> DMSSMN109S Virtual storage capacity exceeded
>
> DMSABE148T System abend 878 called from 0056B246 reason code 00000000
>
> CMS
>
> q cplevel
>
> z/VM Version 5 Release 4.0, service level 1001 (64-bit)
>
> Generated at 03/17/10 13:45:07 MDT
>
> IPL at 03/21/10 07:47:44 MDT
>
> Ready;
>
> q cmslevel
>
> CMS Level 24, Service Level 001
>
> Ready;
>
> q machine
>
> HCPCQV003E Invalid option - MACHINE
>
> Ready(00003);
>
> q v stor
>
> STORAGE = 8M
>
> Ready;
>
> I'm (obviously) pretty VM-naive. What do I need to do?
> Just ask my admin for a bigger machine? How big, nowadays?
>
> Thanks,
> gil
>
--
-- R; <><
