This is exactly what I was going to point to:
REXXSTRF: ENABLE

https://www.ibm.com/docs/en/z-netview/6.4.0?topic=statements-defaults
https://www.ibm.com/docs/en/z-netview/6.4.0?topic=descriptions-defaults-nccf


REXXSTRF
Specifies whether the NetView operator can run REXX command lists that use
the REXX STORAGE function.
ENABLE
Indicates that the NetView operator can run REXX command lists that use the
REXX STORAGE function.
DISABLE
Indicates that the NetView operator cannot run REXX command lists that use
the REXX STORAGE function. DISABLE is the default.

Note: The DEFAULTS REXXSTRF command is effective the next time a REXX
environment is initialized, which is determined by the current REXXENV
value and the number of active REXX command lists. Thus, it is never
effective in the same command list invocation from which it is issued.

On Mon, Dec 19, 2022 at 10:31 AM Cieri, Anthony <
[email protected]> wrote:

>
>         Did you check the value of REXXSTRF in the netview defaults???
>
>         Try a LIST DEFAULTS command in Netview and be sure that the values
> for REXXSTRF is ENABLE
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Jack Zukt
> Sent: Monday, December 19, 2022 8:20 AM
> To: [email protected]
> Subject: Rexx function STORAGE with weird behavior on Netview
>
> [[ SEI WARNING *** This email was sent from an external source. Do not
> open attachments or click on links from unknown or suspicious senders. ***
> ]]
>
>
> Hi,
>
> My colleagues come to me with a weird situation for which I cannot find an
> explanation.
>
> You are probably familiar with the IPLINFO REXX. It works just fine but
> there is one system on which, when invoked by NETVIEW, the
>
> CVT      = C2d(Storage(10,4))                /* point to CVT         */
>
> instruction fails by not returning a value:
>
> IRX0044I Error running ASVTASID, line 42: Function did not return data
>
> As I said before, it works fine on every system and when running under
> NETVIEW, except on this one system.
>
> Any ideas where to look for the reason for this behavior?
> Thank you all for your help,
> Regards,
> Jack
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to