Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Re: RXSUBCOM / ISPD117 / INSUFFICIENT VIRTUAL STORAGE TO EXECUTE COMMAND

473 views

Skip to first unread message

Van Daele Philip

unread,

Nov 10, 2004, 3:56:07 AM11/10/04

Roberto,

IKJ56423I REGION SIZE 2096128 EXCEEDS LIMIT SIZE 0008192
IKJ56429A REENTER -

So I put the logon region limit to 0008192
But this didn't help :-((

Greetz,
Philip Van Daele

-----Oorspronkelijk bericht-----
Van: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] Namens
Roberto Halais Kareh
Verzonden: dinsdag 9 november 2004 17:30
Aan: TSO-...@VM.MARIST.EDU
Onderwerp: Re: RXSUBCOM / ISPD117 / INSUFFICIENT VIRTUAL STORAGE TO
EXECUTE COMMAND

Check yout TSO logon screen for SIZE parameter. I have 2096128
specified.

-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU]On Behalf
Of Van Daele Philip
Sent: Tuesday, November 09, 2004 11:01 AM
To: TSO-...@VM.MARIST.EDU
Subject: Re: RXSUBCOM / ISPD117 / INSUFFICIENT VIRTUAL STORAGE TO
EXECUTE COMMAND

Hi Dave,

It's a very small rexx exec.

/* REXX : DB/2 TimeStamp
*/
/***********************************************************************
*******/
TRACE I

SELSTMT = "select current timestamp" ,

"FROM SYSIBM.SYSdummy1"

ADDRESS TSO "SUBCOM DSNREXX"

S_RC = RXSUBCOM('ADD','DSNREXX','DSNREXX')

ADDRESS DSNREXX "CONNECT DB2O"

ADDRESS DSNREXX "EXECSQL DECLARE C1 CURSOR FOR S1"

ADDRESS DSNREXX "EXECSQL PREPARE S1 FROM :SELSTMT"

IF SQLCODE >< 0 THEN CALL PROC01

ADDRESS DSNREXX "EXECSQL OPEN C1"

say sqlcode

say sqlerrmc

ADDRESS DSNREXX "EXECSQL FETCH C1 INTO :RNAME"
do while SqlCode = 0
say RNAME
ADDRESS DSNREXX "EXECSQL FETCH C1 INTO :RNAME"
end

ADDRESS DSNREXX "DISCONNECT"
say sqlcode
say sqlerrmc

exit 0

PROC01:
say SqlCode
say SqlErrMc
exit 8
RETURN

I saw it on this list a time ago.

Greetz,
Philip Van Daele

-----Oorspronkelijk bericht-----
Van: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] Namens
Seibert, Dave
Verzonden: dinsdag 9 november 2004 12:15
Aan: TSO-...@VM.MARIST.EDU
Onderwerp: Re: RXSUBCOM / ISPD117 / INSUFFICIENT VIRTUAL STORAGE TO
EXECUTE COMMAND

Hello Philip

Are you doing other work in the Rexx exec which consumes lots of
resource?

For example, do you have any stem variable sets with large numbers of
items?

The most common cause I have seen to the Insufficient Virtual Storage
problem has been great volumes of variables, usually stems.

Dave

The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please notify
us immediately and then destroy it.

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions, send
email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

Marcel Harleman

unread,

Nov 10, 2004, 10:44:07 AM11/10/04

Philip,

you tried REGION=0M (in batch) and that didn't work. To me that suggests that the problem is your private area beneath the 16M-line.

Some time ago we ran into storage problems under the 16M-line and after we changed the value of the SWA-variable for all JOBCLASS-definitions in SYS1.PARMLIB(JES2PARM) from BELOW to ABOVE we haven't had any problems beneath the 16M line anymore.

Have you z/OS or OS/390 sysprog check the value. Maybe that's causing the problem.

HTH

Marcel.

0 new messages