You can't share a CF LPAR between sysplexes. You should define at least 2
CF LPARs. And you should avoid - if at all possible - having CF LPARs
sharing ICF processors (unless you really don't care about performance).
Cheers, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Hi Beat,
I've had numerous problems with weird behavior of the software when
datasets were allocated on EAV volumes with the data set extended
attribute (EATTR) set to Opt and the software was not prepared for
this. EATTR=OPT allows the data set to reside in the extended
addressability are ov EAV
I'd have thought that CICS (in particular), in an early stage
of startup when it runs authorized, would set the
Storage-Protection-Override Control (bit 39 of CR0) if
STGPROT=YES was specified as a DFHSIT parm.
Storage protection override is set for everyone in z/OS and has been
pretty much
On Fri, 29 Aug 2014 17:47:03 -0500, Paul Gilmartin paulgboul...@aim.com wrote:
_UNIX03=NO cp -B -P'SPACE=(1,(0,300)),BLKSIZE=0' /dev/fd/0
//TEMP.CBT854.ZIP
As I understand the JCL SPACE parameter, SPACE=(1,(0,300)) asks for a
primary space allocation of 0, with a secondary space
On Aug 29, 2014, at 11:43 PM, retired mainframer wrote:
The ACS routines once existed in source somewhere. When they are
compiled into an SCDS the DSN and member names are saved in the
SCDS also. However, nothing prevents them from being modified
after compilation. (This is no different
