On Fri, 11 Jul 2014 00:32:02 -0400, Robert A. Rosenberg wrote:
At 15:14 -0500 on 07/10/2014, Tom Marchant wrote about Re: SMP/E
APPLY CHECK failing:
Most likely you have DISP=OLD on SCEELKED. It should be SHR.
True. OTOH, this is also fall-out from the allocation ENQs being
broken for years.
The result when running TSO TEST in batch under an 8 char userid is shown below.
//BATCH EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
TEST *(IEBGENER)
L 10.%%+4%+b4%+108% x L(17)
END
The first 7 bytes will be PSCBUSER.
All bytes are blank (x'40') and the length value at the
WARNING: I'm not working with RMM, but ...
Mike Wood wrote:
rmm uses the volser provided by the TS7700 via OAM to track what you are doing
and does whatever is necessary to allow the change to NL and, probably
unfortunately, I suspect it will insist on relabelling back to SL on return to
Hi Rob,
You could carefully check your SMP/e zones. Make sure that you are working
with the CSI you need.
A potential quick fix. Have a look at the DDEFs. Update the DDEF to correct or
add the volser. Try your APPLY CHECK again.
HTH,
Linda
Sent from my iPhone
On Jul 10, 2014, at 10:21
GIM54701E ** ALLOCATION FAILED FOR SMP00027 - IKJ56246I DATA SET
CEE.SCEELKED NOT ALLOCATED, FILE IN USE.
GIM54601E ** DYNAMIC ALLOCATION FAILED FOR SMP00027 BECAUSE SCEELKED
IS PART OF THE SMP00027 CONCATENATION BUT WAS NOT ALLOCATED.
GIM69149E ** CALLLIBS COULD NOT BE
Our z196 3174 consoles are defined on a TYPE=CNC escon chpid. We will
be using a zEC12
at a DR site for testing. Can the console virtual devices on our IODF
TYPE=CNC chpid be attached
to DR site VM devices on a real TYPE=FC chpid? Will our chpid/devices
vary online ok?
--
Donald J.
On Thu, 10 Jul 2014 23:02:50 -0500, Ed Gould wrote:
When SMPE builds the input to the link editor (binder) it does this:
include (ddname of the library the module is included from ie
alinklib (as an example) include alinklib(iew)
I see.
And, in a recent case in my experience, where a ++MOD
On Thu, 10 Jul 2014 18:56:26 -0500, Paul Gilmartin wrote:
Nope. I'll need help on that.
I see Kurt Q has (re-)surfaced.
It would be prudent to listen primarily to him.
Shane ...
--
For IBM-MAIN subscribe / signoff / archive
On Fri, 11 Jul 2014 00:32:02 -0400, Robert A. Rosenberg wrote:
this is also fall-out from the allocation ENQs being
broken for years. The RNAME being used is DSN NOT DSN+VOLSER like
ISPF does. There is NO valid reason to issue an exclusive ENQ on a
dataset name without qualifying it by what
We have 3270 type consoles defined on a 3174 type controller with
TYPE=CNC also. They are actually on Ficon channels which go through an
Escon converter. Anyway, that is background on our home
configuration. It looks similar to yours.
Our D.R. is done at Sungard, under VM. The 3270 console
As already mentioned, you'll be fine.
Regarding SPECIAL from Chapter 17 of z/VM CP Planning and Administration
(SC24-6178):
The SPECIAL statement defines special virtual devices, which are fully
simulated by CP and not connected with real devices at definition time.
It is a good chapter to
This keeps getting better. So I will attempt to provide a more complete
picture.
JCL
//SMPER1 EXEC PGM=GIMSMP,REGION=0M,
// PARM='PROCESS=WAIT'
//SMPCSI DD DISP=SHR,DSN=SMPE.DB2G900.GLOBAL.CSI
//SMPOUT
On Fri, 11 Jul 2014 12:40:01 -0400, Rob JACKSON wrote:
This keeps getting better. So I will attempt to provide a more complete
picture.
//SMPER1 EXEC PGM=GIMSMP,REGION=0M,
// PARM='PROCESS=WAIT'
//...
Why did you hard code dynamic DD's? These statements caused your problem. Never
hard code dynamic DD statements.
Use of specific dynamic DD names is determined by SMP/e and are not consistent
in allocation. SMP00027 may be C related this time but the next run could use
it for something
W dniu 2014-07-11 16:07, Donald J. pisze:
Our z196 3174 consoles are defined on a TYPE=CNC escon chpid. We will
be using a zEC12
at a DR site for testing. Can the console virtual devices on our IODF
TYPE=CNC chpid be attached
to DR site VM devices on a real TYPE=FC chpid? Will our
I was able to resolve the condition with the following actions:
Invoke the SMP/E dialogs ‘Administration’ Action.
Definition
DDDEF
Add definition for SCEECPP
Ran the following Job
//SMPER1 EXEC PGM=GIMSMP,REGION=0M,
// PARM='PROCESS=WAIT'
_IBM to invest $3 bln for chip research and development - Tech2_
(http://tech.firstpost.com/news-analysis/ibm-invest-3-bln-chip-research-development-22
7132.html)
--
For IBM-MAIN subscribe / signoff / archive access
In
0f990dc213e6fe4c9539d02818273f8c7b1bb...@mcexchmbx01.mclane.mclaneco.com,
on 07/09/2014
at 08:52 PM, Sam Bass sam.b...@mclaneco.com said:
There are at least two TSO control blocks that have a 7 char
userid followed by a 1 byte length. I remember someone back in the
MVT days that someone
In 045501cf9b4f$9f5df3d0$de19db70$@mxg.com, on 07/09/2014
at 03:27 AM, Barry Merrill ba...@mxg.com said:
While I clearly didn't recollect the correct command names, I do
remember specifically that when one of the commands that used TPUT
was encountered in the list of commands in my benchmark
In 2104291439117353.wa.paulgboulderaim@listserv.ua.edu, on
07/09/2014
at 05:07 PM, Paul Gilmartin
000433f07816-dmarc-requ...@listserv.ua.edu said:
But I think it's fair in a sense to call ISPF the GUI enhancement
above the TSO READY prompt.
IMHO that would be the TSO Session Manager;
I was able to resolve the condition with the following actions:
Invoke the SMP/E dialogs ‘Administration’ Action.
Definition
DDDEF
Add definition for SCEECPP
Glad to hear you resolved the trouble. However, your explanation
doesn't make sense to me. The error you reported to the list was
I do not understand why anyone currently uses SMP/E JCVL containing any more
than the bare minium od hardcoded DD statements.
//SMPEAP EXEC PGM=GIMSMP,COND=(0,NE),REGION=0M,TIME=NOLIMIT,
// PARM='PROCESS=WAIT'
//SMPCSI DD
On Fri, 11 Jul 2014 19:49:29 +, Gibney, Dave gib...@wsu.edu wrote:
I do not understand why anyone currently uses SMP/E JCVL containing any more
than the bare minium od hardcoded DD statements.
//SMPEAP EXEC PGM=GIMSMP,COND=(0,NE),REGION=0M,TIME=NOLIMIT,
// PARM='PROCESS=WAIT'
Don't ya think it's just rerun from generated JCL trying to get around
incomplete SMP/E DDDEFs?
In a message dated 7/11/2014 3:00:30 P.M. Central Daylight Time,
m...@mzelden.com writes:
I for one like to include the SYSOUT DDs because I don't like separate
output
for each SET
Could be, I never did find the JCL generation dialogs useful and intuitive
enough. :)
And I like the segregation provided by the SYSOUT DDs being dynamic by DDDEF.
To each his own.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of
On Fri, 11 Jul 2014 19:49:29 +, Gibney, Dave wrote:
I do not understand why anyone currently uses SMP/E JCVL containing any more
than the bare minium od hardcoded DD statements.
//SMPEAP EXEC PGM=GIMSMP,COND=(0,NE),REGION=0M,TIME=NOLIMIT,
// PARM='PROCESS=WAIT'
On Fri, 11 Jul 2014 15:39:10 -0500, Paul Gilmartin wrote:
Gee, for this one-off,
I'll do an APPLY pointing an SMP/E library to my data set instead of one
in the DDDEFs. ...
Are you saying that you will sometimes override a target library DDDEF
during APPLY to use a data set that is not part of
And I'd guess your guess is righteous!
Makes sense, now.
Barry
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Thursday, July 10, 2014 8:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Authorizing 8
ISPF is more like DOSSHELL on DOS 4.0.
On Thu, Jul 10, 2014 at 8:50 PM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In 2104291439117353.wa.paulgboulderaim@listserv.ua.edu, on
07/09/2014
at 05:07 PM, Paul Gilmartin
000433f07816-dmarc-requ...@listserv.ua.edu said:
29 matches
Mail list logo
