Working link for current 3270 Data Stream

2020-09-26 Thread Seymour J Metz
The URL 
https://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/cn7p4000/CCONTENTS?SHELF=EZ2HW125&CASE=&DT=19920626112004&usg=AOvVaw284FCQEZQVhAEhwgFFIMTT
 for GA23-0059-07 3270 Data Stream Programmer's Reference
gives me Internal Server Error. The most recent copy t bitsavers is -4. Does 
anybody have a working URL for the current version?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SYSCALL environment not available

2020-09-26 Thread Paul Gilmartin
On Sat, 26 Sep 2020 09:22:27 -0500, Bill Giannelli wrote:

>I added a command "syscalls('ON')" and it now worked fine..
> 
In the M&C at 
https://docs.bmc.com/docs/messages/messages-bmcbmr01-through-bmcbmr99-718473906.html
I see merely:
User response: Establish a SYSCALL environment.

They could be more explicit and recommend SYSCALLS( 'ON' )
That's worth an RCF.  Does BMC have an RCF process?

Regardless, if ISR requires a SYSCALL environment, they should issue
SYSCALLS( 'ON' ) in their code rather burdening the user with it.
If it's redundant, there's no harm beyond a negligible performance
cost.  And that could be mitigated by calling the function only for
error recovery.

That's worth an RFE.  Does BMC have an RFE process?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SYSCALL environment not available

2020-09-26 Thread Bill Giannelli
I added a command "syscalls('ON')" and it now worked fine..

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SYSCALL environment not available

2020-09-26 Thread Dale R. Smith
On Sat, 26 Sep 2020 08:18:48 -0500, Bill Giannelli  
wrote:

>I am trying to run obtain maintenance from BMC thru an ISR (Internet Service 
>Retrieval) and it is failing on a rexx command for USS "address syscall ".
>BMC has said that the "SYSCALL" environment is not available on my system. 
>What is the "SYSCALL" environment and how might I get it available?
>thanks
>Bill

Could the problem be that the userid running the REXX program does not have an 
OMVS segment and/or UID assigned to it?

-- 
Dale R. Smith

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: SYSCALL environment not available

2020-09-26 Thread Paul Gilmartin
On Sat, 26 Sep 2020 08:18:48 -0500, Bill Giannelli wrote:

>I am trying to run obtain maintenance from BMC thru an ISR (Internet Service 
>Retrieval) and it is failing on a rexx command for USS "address syscall ".
>BMC has said that the "SYSCALL" environment is not available on my system. 
>What is the "SYSCALL" environment and how might I get it available?
>
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.bpxb600/syscenv.htm

I'm astonished. 
The SYSCALL environment can be used by any REXX program with syscall
commands, whether it runs from TSO/E or the z/OS shells (where the
environment is automatically initialized).

(I'd add IRXJCL to that list.)

Are you running under z/OS, but perhaps in a captive environment with
limitations on host environments?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


SYSCALL environment not available

2020-09-26 Thread Bill Giannelli
I am trying to run obtain maintenance from BMC thru an ISR (Internet Service 
Retrieval) and it is failing on a rexx command for USS "address syscall ".
BMC has said that the "SYSCALL" environment is not available on my system. What 
is the "SYSCALL" environment and how might I get it available?
thanks
Bill

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN