> There is another problem COMECBPT is key 0 storage and MY_ECB is key
> 8 WAIT requires the user to be in the key of the ECB would I have the
> that problem using SELECB
Except for the communications ECB!
There is a special check in wait for the communications ECB to allow
problem key callers to
I have to create an ACEE in the init module because the jobstep runs in user
mode. That work fine currently. I will find a better sub-pool to use.
Thanks
Robin
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Relson
Sent: 15 Janua
Hi,
I am trying to install an ISV product.
The product was delivered as 3 XMITed libraries.
I used RECEIVE to create the product libraries.
When I try to edit members in the libraries, I get a message that edit is not
allowed because they are under SCLM control.
SCLM is being used for application
You can access hiperspaces in COBOL using the MVS Callable Services for
HLLs Window Services
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieac100/ws.htm.
There are code examples.
On 15/01/2019 2:58 am, scott Ford wrote:
Peter:
My typos ..sorry the question was
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Edward Finnell
> Sent: Monday, January 14, 2019 4:05 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: HCD question
>
> Don't forget to update LOAD and PARMLIB values.
True. I'm at
Thanks Ed. I do remember that first discussion now, I think I got busy at work
and missed following the other longer one.
Hmm-m-m. Maybe an RCF for PoOp complaining about the lack of examples for many
of the more recent complex instructions, including vectors and the several
newer "PERFORM .
Don't forget to update LOAD and PARMLIB values.
In a message dated 1/14/2019 4:24:49 PM Central Standard Time, gib...@wsu.edu
writes:
It will all fit on a Mod 27. As below, Start with Mark Zelden's example. Tailor
for your needs.
-
Sounds like a SHARE presentation to me!
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Farley, Peter x23353
Sent: Monday, January 14, 2019 11:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Unreadable code (Was: Concurrent S
On 1/14/2019 11:18 AM, Farley, Peter x23353 wrote:
I also participate in ASSEMBLER-LIST and I don't remember such a discussion.
Can you pinpoint the approximate time period for that discussion?
My biggest complaint/concern with the vector instructions is the woeful lack of
any example code sh
It will all fit on a Mod 27. As below, Start with Mark Zelden's example. Tailor
for your needs.
I did find that a separate SYSCAT volume made the subsequent steps of recovery
easier.. I IPL the single system to refresh the other copy of the single system
and a resuce SYSCAT, then IPL each Lpar (
See Mark Zelden's Utilities.
Or just make it yourself, it's not black magic.
Recipe:
Review your sandbox/tech system. Note all your volumes. Try to put as
much as possible on same volume. Shrink opeational datasets (page,
spool, RACF db) as possible.
Delete all SMPE operational datasets (CSI, LT
Thanks guys,
very helpful.
Peter, I have tested with LLA stopped,thought I posted that test.Still
received S106-C.
Since the problem started with CICS 5.3, I think a PMR with CICS is the
next step.
I'll run more tests today (I'm at a different client today).
Wayne
On Tue, Jan 15, 2019 at 3:0
Ed,
I also participate in ASSEMBLER-LIST and I don't remember such a discussion.
Can you pinpoint the approximate time period for that discussion?
My biggest complaint/concern with the vector instructions is the woeful lack of
any example code showing how to use them for just the kind of funct
> I've taken to defining functions in header files to take advantage of both
> (we don't use IPA).
Looking at the code generated by the XLC compiler, I see that it sometimes
(often?) in-lines functions even when they are defined in the (same, obviously)
implementation file.
Charles
-Orig
Peter:
My typos ..sorry the question was in regard to a Cobol program creating and
then referencing
Hiperspaces. You answer was what I thought, so thank you.
Scott
On Mon, Jan 14, 2019 at 12:59 PM Peter Relson wrote:
>
> > So how does a Cobol Pgm , 31bit address say a Hiperspace ?
> > I assum
File-AID/MVS should provide what you are looking for using option 3.1, Library
Utilitiy.
File-AID - Directory Information ---
COMMAND ===>
Dataset: PFHKXC0.USER.ISPLLIB(ESSCOBL) TTR 24
- - - - - - - - - - - - Directory en
On 1/13/2019 8:47 PM, David Crayford wrote:
IIRC, the interleaved instruction scheduling was to mitigate the AGI
problem?
Yes. The AGI "problem" is still there, but with an OOO machine you can
avoid it simply by using different registers rather than by completely
reordering your code.
In
> So how does a Cobol Pgm , 31bit address say a Hiperspace ?
> I assume an interface program units AR registers , etc., am I correct ?
> I have don’t this want to...
I could not parse this. What were you trying to ask?
Hiperspaces are not directly referenced. You use services to put data in
an
I am thinking storage in a user sub-pool and saving the address in the
ACEE since we create that.
An ASCRE Initialization routine must not obtain storage in user-region
subpools because after the initialization routine runs, the user region is
(re-)initialized.
Maybe you shouldn't be creati
Guys:
I want to build a three pack rescue system , where do i find the 'how to '
...??
Scott
On Mon, Jan 14, 2019 at 10:51 AM R.S.
wrote:
> W dniu 2019-01-14 o 13:16, Tony Thigpen pisze:
> > We have a 3-pack rescue system that was built by a person long-gone.
> > On the 3-pack system, there ar
On Mon, 14 Jan 2019 08:30:20 -0600, Tom Marchant wrote:
>On Sat, 12 Jan 2019 14:59:05 +1100, Wayne Bickerdike wrote:
>
>>Step end stats:
>>
>>IEF032I STEP/STEP020 /STOP 2019011.2148
>>
>>CPU: 0 HR 00 MIN 00.05 SECSRB: 0 HR 00 MIN 00.01
>>SEC
>>VIRT: 7908K SYS:
W dniu 2019-01-14 o 13:16, Tony Thigpen pisze:
We have a 3-pack rescue system that was built by a person long-gone.
On the 3-pack system, there are several IODF files. I need to update
the current IODF file.
But, the IODF files on the rescue packs are not cataloged to the
production z/OS. Whe
I agree with Skip, working in Security, i.e. ; RACF etc, usually exits
enforced rules , such as passwords or installation restrictions and / or
standards.
Scott
On Fri, Jan 4, 2019 at 10:02 PM Jesse 1 Robinson
wrote:
> Tom and I grappled with a menagerie of system exits that had been adopted
>
I'd still like Wayne to post the untruncated CSV031I message...
(or re-post it if he had done so but I missed amidst the many appends).
Check out the reason code of the S106-xx message. It could be that the
module it's trying to load is in LLA, but LLA REFRESH was not done after
replacing the
On Sat, 12 Jan 2019 14:59:05 +1100, Wayne Bickerdike wrote:
>Step end stats:
>
>IEF032I STEP/STEP020 /STOP 2019011.2148
>
>CPU: 0 HR 00 MIN 00.05 SECSRB: 0 HR 00 MIN 00.01
>SEC
>VIRT: 7908K SYS: 260K EXT:4K SYS:10876K
>
>ATB- REAL:
> On Jan 11, 2019, at 11:14 PM, Brian Westerman
> wrote:
>
> Since it does use Adabas, maybe EntireX is the proper answer for this.
Right. Also, you mentioned COM-PLETE, which has some ability to act as a web
server. You might investigate that.
--
Pew, Curtis G
curtis@austin.utexas.edu
Hi Tony,
You could use IDCAMS with DEFINE RECATALOG (before invoking HCD).
Regards,
David
On 2019-01-14 07:52, Tony Thigpen wrote:
> Thanks, Sounds like EXPORT/IMPORT is the best way. I was hoping for
> some 'trick' with the panels, but I guess not.
>
> Tony Thigpen
>
> Gadi Ben-Avi wrote on 1/1
Thanks, Sounds like EXPORT/IMPORT is the best way. I was hoping for some
'trick' with the panels, but I guess not.
Tony Thigpen
Gadi Ben-Avi wrote on 1/14/19 7:22 AM:
This is a job I use to copy an IODF to another system.
//DEL EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//DD1 DD DISP=SHR,UNIT=3390
This is a job I use to copy an IODF to another system.
//DEL EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//DD1 DD DISP=SHR,UNIT=3390,VOL=SER=Z23R01
//SYSIN DD *
DELETE SYS1.IODF15.CLUSTER FILE(DD1) CATALOG(ICFCAT.MCATZ23)
SET MAXCC = 0
//DSSC0087 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SYSIN D
Why not just export your IODF files from your production system and import them
onto the rescue system volume?
Or import/connect the catalog on the rescue system to your live system and use
a different hlq (e.g. SYSR.) for those data sets?
Just two thoughts - hope this helps.
-
We have a 3-pack rescue system that was built by a person long-gone. On
the 3-pack system, there are several IODF files. I need to update the
current IODF file.
But, the IODF files on the rescue packs are not cataloged to the
production z/OS. When I use the HCD panels, it does not appear that
31 matches
Mail list logo
