On 2018-02-10 00:30, Charles Mills wrote:
That is how the C/C++ compiler works. PARM='OPTF(DD:SYSOPTF)' or any other
valid DD name, or DSN, or zFS name. Only one name, though.
Enterprise PL/I allows multiple DD names, like:
//IBMZPLI EXEC PGM=IBMZPLI,
// REGION=0M,
// P
This was from a WAS 8.5 install
Upgrade WASAS850, Subset HBBO850
http://www-01.ibm.com/support/docview.wss?uid=isg1_WASAS850_HBBO850
I used Google and search terms IBM HBBO850
If your existing copy of the WebSphere Application Server
Liberty profile includes the extprogmodels i
Mr. Tom Ross,
Yes, we use the OPTFILE compiler option in the PARM= parameter
exclusively. Via JCL SET statements we establish the PDS and member
name to use for the DD SYSOPTF file. This allows us to point to
different members for different COBOL compile types (i.e. batch, CICS,
test compil
This is a monoplex... The program directory of the product didn't mention
about this mount points ... It sounded like a product bug...
On 10-Feb-2018 8:17 PM, "Lizette Koehler" wrote:
> Some Questions
>
> Is the LPAR this is running on, where the mount files reside?
>
> For example, you only h
Some Questions
Is the LPAR this is running on, where the mount files reside?
For example, you only have one LPAR this can run on? Or is this a SYSPLEX and
it can run on more than one system?
If this is a sysplex, make sure the file mounted where the job runs. To do
this, logon that that syst
Hi
While applying an FMID for the WAS V10 I received the below error
Error Message: BPXF140E RETURN CODE 0081, REASON CODE 0594003D. A LINK
FAILED FOR LINK NAME /usr/lpp/InstallationManagerRepository /HBBO850/IBM/..
/WLP/fixpac. Pls find the attached log .
I see a similar issue reported to
>Will the Segment created by IARV64 be visable in a dump
>when the program issues ABEND ,DUMP,STEP
A true z/OS answer: it depends.
For SYSABEND/SYSUDUMP: no.
For SYSMDUMP, I think, yes.
There is no support for 64-bit storage in the "formatted dump" variants.
Peter Relson
z/OS Core Techno
