Re: FRBACKUP Still Not Working...

In this situation, we have used the TSO command: TSO fcwithdr tdevn() with some success. I'm afraid that is just a way around the problem rather than an explanation of what exactly the problem is. Best regards, David Tidy IS Technical Management/SAP-Mf

Re: sadump (and autoipl)

As regards the HLQ part, we have successfully used a non-SYS1 SMS managed 4xm27 dataset for the non-prompt AUTOIPL Sadump: AMDSADMP IPL=D3390,VOLSER=SD, OUTPUT=(DBD36,PXSYS.OPER.SADMP), DDSPROMPT=NO, MINASID=ALL,

Re: TSO on z/OS 1.12 with LOGONHERE and multisystem logon

Hi Jon, To address the Console issue here, we force the SDSF variables on the way in with this code: sysname = mvsvar('SYMDEF','SYSNAME') isfcons = userid()||RIGHT(sysname,1) isfsysid = sysname Address ISPEXEC VPUT (ISFCONS

Re: NetView Startup problem

Hi Saurabh, I haven't followed this one much so I hope I am not repeating earlier advice, but ACNMLINK certainly won't work - you need your target library for sure (lowest level qualifier CNMLINK - I can't remember the prefixes, but it might be TLIB.NV390.V5R3.CNMLINK for you) and it must be

Re: NetView Startup problem

My earlier reply was based on the Netview 5.3 mentioned in the dataset name (the SSN statement changes in version 6). Best regards, David Tidy IS Technical Management/SAP-Mf Dow Benelux B.V. -Original

Re: NetView Startup problem

, and CNMINIT member exist in this. DLIB.NV390.V5R3.ACNMLINK(CNMINIT) Thanks Regards SAurabh On Thu, Nov 24, 2011 at 4:54 PM, Tidy, David (D) dt...@dow.com wrote: Hi Saurabh, I haven't followed this one much so I hope I am not repeating earlier advice, but ACNMLINK certainly won't work - you

Re: How do you manage CALLLIBS for products not installed?

Hi, I deleted the System Automation FMID for the IMS stuff. Where we do have the product, I just point to the appropriate place (ready to forget when we are running two levels of CICS for instance). Best regards, David Tidy Tel:(31)115-67-1745 IS Technical

Re: +DFHAP0001 CICS An abend (code 0C4/AKEA) has occurred at offset X'FFFFFFFF'

Hi John, There is an IBM link for further investigating dumps like this (offset x''): http://www-01.ibm.com/support/docview.wss?uid=swg21424768 . I normally follow that to get to the real PSW location. (This one is for CICS 4.1, but it does include a link to the process for other

Re: How to find out DFHSM intentions ?

Hi, I don't think there is an out dataset option for QUERY. In SYS1.SAMPLIB(ARCTOOLS) there is a queryset REXX which returns the output to TSO via extended console processing. We basically use a version of QUERYSET to get HSM output back to TSO, and then we have other routines that issue any TSO

Re: What Datasets have been Migrated to ML2

We run a batch TSO job with: HSEND LIST DSN SELECT(AGE(190)) - ODS(datasetname) - this lists all migrated datasets older than 190 days (that is to reduce the size of the output) - you can also use Patch commands to increase the allocation parameters of the output dataset - like:

Re: IPLTEXT and NUCLEUS dates

Hi, We have our sandbox system where we run SMP/E - and it's the only system where SMP/E is installed. We do choose to apply maintenance on this running system in general (yes - we know that this may not be the recommended approach). It's a bit theoretical, but should someone manage to apply an

Re: IPLTEXT and NUCLEUS dates

It is true that there is some exposure in our maintenance strategy. However we always have multiple versions of our cloned sysres availabe to IPL from, and we do have a backup strategy to get back to the pre-maintenance level. That's why I keep saying the wait state itself is not really an issue

Re: IPLTEXT and NUCLEUS dates

Although this isn't too much of a risk for us, I do have to say that protecting IBM from having to diagnose my problems by putting my SMP/E system into a wait state doesn't quite match what I would hope for as a customer. Best regards, David Tidy IS Technical

Re: re-locating the cursor into the primary command line within an ispf edit macro

The manual indicates: Note: To position the cursor on the command line, issue a return code of 1 from the macro. For example, in CLIST code EXIT CODE(1) as the last statement in your EDIT MACRO to position the cursor on the command line. Best regards, David Tidy

Re: ISPF: How best to change ISPSPROF variables programmatically (was ISPF: How best to change user variable ZRETMINL in ISPSPROF)

Hi Dave, That helps enormously - thanks! Best regards, David Tidy Dow Benelux B.V. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Dave Salt Sent: 12 August 2010 17:01 To:

ISPF: How best to change ISPSPROF variables programmatically (was ISPF: How best to change user variable ZRETMINL in ISPSPROF)

Hi, I was actually hoping to see a response to something more similar to Mark's interpretation. In particular I wanted a programmatic (REXX) way to (re)set the tab to point and shoot fields on the way in to TSO/ISPF. This in particular because MXI turns it on, but of course if you time out, it is

CICS Poster (was C-I-C-S vs KICKS)

I did eventually find my CICS poster, but you can't have it. I can take a picture that is readable if you zoom in (but it will be 4mb file size)- I'll need to be home in good light though, as otherwise reflections get in the way. Let me know, and I can send it to you offline. I also have another

Re: Can't delete datasets

Typically we have had to resort to VVDSFIX for this kind of situation. Read all about it (+ link for the download) at: http://www-01.ibm.com/support/docview.wss?uid=isg3S1000618 Best regards, David Tidy IS Technical Management/SAP-Mf Dow Benelux

Re: ICHRDSNT

Not directly related, but in case it relates to the reason behind the original question, we need to maintain two copies of ICHRDSNT - our 'standard' sysplex one, and a non-sysplex one for the first DR IPL. We do this by having the standard one in linklib, and keeping the DR copy in a dedicated

Re: ICHRDSNT

, Tidy, David (D) dt...@dow.com wrote: Not directly related, but in case it relates to the reason behind the original question, we need to maintain two copies of ICHRDSNT - our 'standard' sysplex one, and a non-sysplex one for the first DR IPL. We do this by having the standard one in linklib

Re: ICHRDSNT

Walt - thanks for the confirmation - that indicates our DR construct should work OK. I think we might still test first though! Best regards, David Tidy Dow Benelux B.V. -Original Message- From: IBM Mainframe Discussion List

Re: Defrag

Oh dear - I feel a bit guilty just trying to answer the original question, but anyway here's how we do it. We use the tools System Automation and MXI in the process, and what we do is at every JES2 shutdown (i.e. pre-IPL shutdown as far as intent goes, and our IPLs are monthly), we run an SA REXX

Re: Strange JCL error

Have you tried renaming your ISPF profile data set (temporarily) and using a completely fresh one for a session? Best regards, David Tidy Tel:(31)115-67-1745 IS Technical Management/SAP-Mf Fax:(31)115-67-1762 Dow Benelux B.V.

Re: 3592 Cartridges

Hi George, I believe we use the same approach (build backup job via REXX, as you see creating on-site and off-site backups), and our created job looks like this: //ACT103 EXEC LRSTGBKP,PAC=ACT103 //* //SCT100 EXEC

Re: SDSF PREFIX Enhancement (UK44477)

Hi Bob, The PROPLIST that are available are documented in the z/OS 1.10 manual section 2.14. There is no modification bar for the Command.PREFIX.AddGenChar, so I guess it applies to 1.9 as well. This is only for the prefix command, not the extension to H and ST that the APAR mentions (and I

Re: SDSF PREFIX Enhancement (UK44477)

We did actually implement this from z/OS 1.9 onwards, and it was via an entry in ISFPRM parmlib member: PROPLIST NAME(GLOBPROP) /* Group ISFOPER properties */ PROPERTY NAME(Command.PREFIX.AddGenChar),VALUE(TRUE) So maybe that is all that is missing. No user exit needed

Re: SDSF Batch command size limit

Hi, You don't say which release you are, but from 1.9 onwards, you should be able to use the ' option if you use the ISFAFD program to invoke batch SDSF. The following is an example: //EXECSSID EXEC PGM=ISFAFD //ISFOUTDD SYSOUT=*

Re: strange codepage issue in ISPF

Thanks for the earlier correction on my language - I am indeed English. Explains why I couldn't reconcile the hex. I work for an American company as well, so I should have been more aware. Anyway for the original problem, look at what has happened in your ISPF terminal type (under Menu;settings).

Re: strange codepage issue in ISPF

I believe that x'4D' and x'5D' are the CP1047 standard brackets. (x'AD' and x'BD' are square brackets). I looked on http://publib.boulder.ibm.com/infocenter/pcomhelp/v5r9/index.jsp?topic=/ com.ibm.pcomm.doc/reference/html/hcp_reference27.htm which seems to confirm that. I changed my code page in

Re: PDSE question - while discussing checkered history

Hi, We do already use indirect cataloging, but we do want VSAM (and also the catalog) on the volume itself, and don't want to change our whole longstanding set-up because DFDSS can't cope with PDSE satisfactorily. Copying the PDSEs first does seem a less intrusive way to handle IBM's problem.

GRS CNS policy

Hi all, I've just noticed the ability to position the GRS contention notification in a GRS star (OA11382). I did notice that the reasoning for the ability to do this is to better balance workload in a sysplex, but can't find any recommendations as to the positioning. We are running sysplex mostly

Re: PDSE question - while discussing checkered history

Hi Mark, Sorry - I missed that. Interesting that it tends to mention the source dataset allocation rather than the target. It certainly offers an explanation of why the dataset might increase in allocated extents. But in our case it appears to release the secondary allocation - the end result is

PDSE question - while discussing checkered history

Hi, Amongst the current discussion of PDSE, I have a curious problem that I wondered if anyone could explain. I do a logical copy of our SYSRES volume to a new volume, but get the following messages for SYS1.SCUNTBL - a large PDSE: ADR717E (003)-FMSG (02), SYSTEM SERVICES ERROR OCCURRED WHILE

Re: PDSE question - while discussing checkered history

Hi Mark Thanks for the reply. These are newly initialised empty volumes. We do the logical copy because we up-sequence the volume id, and build a new catalog (with the volume id in the name) as we go. Doing the large PDSEs first is a good idea though in terms of getting around the problem,

Re: MVS 4 minute 'outage'

We had Skip's problem (although maybe not the original problem). If your freeze is synchronised with SMF/RMF interval, check II07124 - we added DDCONS(NO) to our SMF parms to resolve that problem (actually for us it was a 30 second freeze, although the APAR states 1-5 minutes). Best regards,

Re: ZFS file made bigger

I've used the ISH ISPF shell - dropdown File systems; zfs aggregates; Extend. It's nice and easy! Best regards, David Tidy Tel:(31)115-67-1745 IS Technical Management/SAP-Mf Fax:(31)115-67-1762 Dow Benelux B.V.

Re: CICS TS 2.2 and z/OS 1.7-

Hi Ken, Without directly answering your question, and without mentioning our details as to what put us in this position, we are currently running quite a few CICS 2.2 regions under z/OS 1.9, and have not so far seen any such problem. At least one is a large DB2 system, although running SAP on

Re: SDSF I (Input) Screen with z/OS 1.9

Hi, POS appears to be working fine for us (with 5 jobs waiting in class O, and 27 in class P). There is also a Wpos column for positions within WLM service classes, but that appears sensibly filled as well. I presume you reworked any ISFPRM customisation from the ISFPRM01 defaults. This

ESQA allocation question

Hello, I've seen earlier items about Healthchecker and its ESQA checking, but I have a general question to which I haven't been able to find the information in the manuals. Given that ESQA will just overflow into ECSA is there any real reason not to allocate ESQA fairly low so that it is always

Re: ESQA allocation question

Hi all, Thanks for the responses and pointer to Kathy's White Paper. It is true that we have INITSQA coded, and that was for IPL failures which we thought were related to additions/changes to the storage configuration. However it did seem that INITSQA did not actually help much - just the action