Re: IEC141I 013-A8: how to read VS data sets?

The S in FS is the same "standard" as the S in FBS. With an F which has been MODded there will, mostly, be an unfilled track (last record on from the previous output, empty remainder of track unless the record happens to be the last one which would fit on a track). FS guarantees (by the person

Re: (External):Re: IEC141I 013-A8: how to read VS data sets?

From the trivia-I-happen-to-know drawer. Classic CA-1 (at least used to) use an unblocked RECFM=F data base so that records could be managed in the same way. So tape volser 123456 would be the 123,456th record in the data base. Made for a gigantic data base, but processing was very quick

Re: IEC141I 013-A8: how to read VS data sets?

I don't think 'FS' is meaningful. Not wrong, just pointless. If unblocked, all blocks contain exactly one record. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com

Re: IEC141I 013-A8: how to read VS data sets?

What does RECFM=FS mean? How does it differ from RECFM=F? Sent from my iPhone > On Jan 5, 2017, at 20:12, Bill Woodger wrote: > > Yet in modern times the S for F has its uses. If a C/C++ program is going to > use a "seek" for a file, if the file is F/FB, then the

Re: IEC141I 013-A8: how to read VS data sets?

Yet in modern times the S for F has its uses. If a C/C++ program is going to use a "seek" for a file, if the file is F/FB, then the file will be read from the start to satisfy the seek (because there may be those embedded short blocks), but if the file is FS/FBS (guarantee, by the person who

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

On 5 January 2017 at 12:38, Pommier, Rex wrote: > 2) $BR1 in M gives me "lots" of good information . > The doc says "JES2 initialization processing encountered an error examining > the BERT maps" and the resolution is " > Use the indicative dump and the SVC dump (if

Re: IEC141I 013-A8: how to read VS data sets?

Pretty much I would say. Just want to point out that FBS and VBS are worlds apart. As discussed, the 'S' in VBS is 'spanned'. The 'S' in FBS means 'standard' or some such. This guarantees that the file has no short blocks other than the very last one. A file written 'normally' is usually FBS

Re: IEC141I 013-A8: how to read VS data sets?

Paul, For QSAM, there's F/FS/FB/FBS, U, V/VB, VS/VBS that you may see used in a business system (and business systems, in the main, are the reasons for having a Mainframe). All have their specific "it's better in this case to do this". Of these, VS/VBS is the slowest way to read or write

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

A sysmod can have more than one ++VER. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Thursday, January 05, 2017 4:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IPLing z/OS 2.2 from 1.13 for first time

Re: IEC141I 013-A8: how to read VS data sets?

On 2017-01-05, at 14:47, Jesse 1 Robinson wrote: > > If a JES2 output segment is created with 'VS' attributes, that does not mean > that the data on spool actually consists of spanned records. The point of > spanning is to manage records that can exceed physical block size, e.g. > 32760. SMF

Re: IEC141I 013-A8: how to read VS data sets?

http://www.redbooks.ibm.com/abstracts/sg247419.html SDSF REXX Redbook Providing REXX programs with an API to access IBM z/OS System Display and Search Facility (SDSF) functions gives you a powerful tool for accessing and controlling JES resources. Although we chose REXX as the language

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

We’re drifting a bit here, but I had to look up ++VER to see whether a single PTF could be installed on more than base FMID. I find '-FMID--(--sysmod_id--)-' I have never made peace with railroad track diagrams, but I think this means that only one base FMID can be specified. I don't see

Re: IEC141I 013-A8: how to read VS data sets?

http://www.redbooks.ibm.com/abstracts/sg247419.html SDSF REXX Redbook Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Elardus Engelbrecht > Sent: Thursday, January 05, 2017 1:50 PM > To: IBM-MAIN@LISTSERV.UA.EDU >

Re: IEC141I 013-A8: how to read VS data sets?

OK, I overstated my case. Did not think about SORT. Certainly ISPF cannot handle VBS. I've long operated on the ROT that you can't do much with SMF data until 'something' converts it to VB, so I have not actually tried standards like IEBGENER or IDCAMS in many a moon. I am curious though as

Re: IEC141I 013-A8: how to read VS data sets?

Jesse 1 Robinson wrote: >Most standard utilities fail when opened to V(B)S records. Please name them. Just so I can shock my amazed users when they complain about reading VBS things... >Only IFASMFDP can read SMF data, and the output from that is ordinary VB. Really? What about DFSORT and

Re: IEC141I 013-A8: how to read VS data sets?

On Thu, 5 Jan 2017 13:50:25 -0500, Carmen Vitullo wrote: >for my own sake I checked some sysout of my own and if you scroll over to the >right in the jes2 dataset view from ? you see jes2 dataset attributes, I see >RECFM V and U and VA and UA, no VS for any jes2 datasets > Ah, but did you

Re: CLOCKxx - ACCURACY Parameter - IEA032E message

> It would seem to me, that for the accuracy keyword to work, that STP > must be using external time sources directly? Or is ACCURACY only > really reporting on clock steering events > 50 milliseconds(in your case)? ACCURACY is looking at the steering information and issuing IEA032E if the

Re: IEC141I 013-A8: how to read VS data sets?

for my own sake I checked some sysout of my own and if you scroll over to the right in the jes2 dataset view from ? you see jes2 dataset attributes, I see RECFM V and U and VA and UA, no VS for any jes2 datasets Carmen - Original Message - From: "Jesse 1 Robinson"

Re: IEC141I 013-A8: how to read VS data sets?

Like Walt, I'm skeptical of the assertion that a spool data set is VS, where 'S' means 'spanned'. Spanned records are extremely rare in MVS. The only use for them I've ever come across is MANx SMF, which I believe predates dirt. Most standard utilities fail when opened to V(B)S records. Only

Re: Addressing Question

All, My intent was clarification for my old age. I went back and looked and I am good. Thanks all.. Scott On Thu, Jan 5, 2017 at 10:24 AM scott Ford wrote: > Tom, > > Thx for you comment. I agree otherwise there is confusion. > > > Scott > > On Thu, Jan 5, 2017 at 4:55 AM

Re: Addressing Question

Tom, Thx for you comment. I agree otherwise there is confusion. Scott On Thu, Jan 5, 2017 at 4:55 AM Tom Marchant < 000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: > On Wed, 4 Jan 2017 16:24:12 -0600, Bill Woodger wrote: > > > > >No. Your CALLs are static. > > > > > > > Bill, > > > >

Re: UTC and Daylight Savings Time

I have not seen anyone mention LPAR time offset. It's been around for years--around Y2K IIRC--but we've never had a need to use it. In the LPAR Image profile, you have this option: Clock Type Assignment Standard time of day Logical partition time offset If you select Standard, the LPAR

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

On Thu, 5 Jan 2017 11:26:51 -0600, Art Gutowski wrote: >... it probably wouldn't hurt to do a REPORT SYSMODS <1.13 zone> >COMPAREDTO(<2.2 zone>) and vice versa. Is that going to give you any useful information, Art? I believe that it is possible to code the ++VER in a PTF so that the same PTF

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

Hi Allan, Thanks for your response. Here's where I am in regards to them. 1) I need to double check compatibility maintenance. The only initialization parameters listed in the migration guide as needing changes are optional (removing BROADCAST from OUTDEF and JCLERR from JOBDEF) and I did

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

From "Pommier, Rex" on Thu, 5 Jan 2017 17:17:01 +: >Thanks for the suggestion. We are already running MODE=DUPLEX. We had one or two systems where we had to make this change, and a couple that we had to migrate to z11 checkpoint format. Other than that, no issues

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

Hi Ravi, Thanks for the suggestion. We are already running MODE=DUPLEX. CKPTDEF CKPT1=(DSNAME=SYS1.HASPCKPA, VOLSER=Z1PG02, INUSE=YES), CKPT2=(DSNAME=SYS1.HASPCKPB, VOLSER=Z1PG03,

Re: UTC and Daylight Savings Time

On Thu, 5 Jan 2017 17:02:23 +, Bill Bishop (TMNA) wrote: >I have been requested to investigate the impact of switching "local" time to >"UTC" time. > >We currently use STP to establish the time and offsets for our LPARs, so >basically we are using UTC time correctly. > >However, the

Re: UTC and Daylight Savings Time

Local time is just that, local - which means the time must adhere to the LOCAL requirement. UTC is the world wide standard time, it will not change for daylight savings. Sent from my Verizon, Samsung Galaxy smartphone Original message From: "Bill Bishop (TMNA)"

Re: UTC and Daylight Savings Time

What is your CLOCK00 entries in SYS1.PARMLIB like? I think if you code: STPZONE NO & TIMEZONE W 00.00.00 You would be running UTC and not be affected by DST & Time Zones Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

Hi Elardus, What do you see if you issue $D ACTIVATE during that disastrous IPL? I couldn't do a $D ACTIVATE because JES was down. Once it came up cold, it shows that I'm in Z22 mode. This is documented and WAD, but very very disruptive! Yup, and not something I want to do. There is

UTC and Daylight Savings Time

I have been requested to investigate the impact of switching "local" time to "UTC" time. We currently use STP to establish the time and offsets for our LPARs, so basically we are using UTC time correctly. However, the requirement may include not changing local time when daylight savings time

Re: IEC141I 013-A8: how to read VS data sets?

On Thu, 5 Jan 2017 21:13:48 +0700, Robin Atwood wrote: >The JCL is not relevant, both applications are servers that use dynamic >allocation. They are using SAPI to read the JES spool. The >message is > >IEC141I 013-A8,IGG0199G,TAURISP3,TAURISP3,SYS2 > >The spool data set

Re: IEC141I 013-A8: how to read VS data sets?

Is this homegrown or vendor product like Mobius, VPS or other like product? There is no obvious reason, short of reading a dump, to know what one job works and one job does not. If vendor product, then I would contact the vendor. Otherwise I would contact IBM - probably JES2 Lizette >

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

On Thu, 5 Jan 2017 08:01:15 -0600, John McKown wrote: >Why not >https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae200/remenq.htm >? IMO, this is better: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idas300/rname.htm -- Tom Marchant

Re: IEC141I 013-A8: how to read VS data sets?

The JCL is not relevant, both applications are servers that use dynamic allocation. They are using SAPI to read the JES spool. The message is IEC141I 013-A8,IGG0199G,TAURISP3,TAURISP3,SYS2 The spool data set is allocated to SYS2. I am really interested in advice about reading VS data

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

These all were old/uncatalog's datasets left on the pack which were used with z/OS1.13 as sysres(way back we moved to 2.1 and now over to 2.2) so as had same name dsn got enqueue with LLA/XCFAS , now as some of you responded being simple was to get the init done however due to storage

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

Why not https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae200/remenq.htm ? On Thu, Jan 5, 2017 at 7:55 AM, Ravi Gaur wrote: > These all were old/uncatalog's datasets left on the pack which were used > with z/OS1.13 as sysres(way back we

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

Also not to miss if you have MODE=DUAL have it changed to MODE=DUPLEX ...There's an APAR regarding it with zOS2.2 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with

Re: How many FRR stack entries are available?

I am writing code that is called by the end-user in SRB mode, and the code will issue a PC. The caller may very well have its own FRR. I would like to have the API have an FRR as well as the PC routine. Is there some programable way I can determine how many are free (if only 1, I would prefer to

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

On Thu, 5 Jan 2017 05:37:08 -0700, Lizette Koehler wrote: > If these are Linklst'd datasets, then you could > 1) Build a new LINKLST and remove these datasets in the new LINKLST > 2) Do what you need to with these files (move, delete) A new LNKLST set without the data sets is not sufficient.

Re: How many FRR stack entries are available?

Peter Relson wrote: >>The manual states "The system only guarantees that installations can add >>two FRRs" >>Is that still true for zOS 2? >Yes it is still true. Thanks! I have searced around, but in what book is that written? > That is not a statement about how much room there is for FRRs

Re: IPLing z/OS 2.2 from 1.13 for first time getting JES2 catastrophic error

I believe z/OS 2.2 fits within the N-2 compat/fallback range so: 1) verify all compat/fallback maint is installed on the 1.13 system. Check for incompatable initialization parameters in the 2.2 JESPARMS. 2) look up $BR1 in JES messages/codes to see if any insight can be gained there 3)Contact

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

On Thu, 5 Jan 2017 03:39:39 -0600, Ravi Gaur wrote: >Delete datasets from Disk/3390 which are having enqueue from LLA/XCFAS It would help if we know what data sets. If they are things like SYS1.LINKLIB on an alternate IPL volume there are acceptable ways to do it including the BYPASSNQ program

Re: How many FRR stack entries are available?

The manual states "The system only guarantees that installations can add two FRRs" Is that still true for zOS 2? Yes it is still true. That is not a statement about how much room there is for FRRs overall in the FRR stack (which, as it has long been, is 16 entries worth). Peter Relson

Re: Addressing Question

On Wed, 4 Jan 2017 16:24:12 -0600, Bill Woodger wrote: >No. Your CALLs are static. > Bill, It would be helpful if you would quote enough of the message that you are replying to to provide context to what your "No" references. -- Tom Marchant

Re: IEC141I 013-A8: how to read VS data sets?

Robin, Please delete any part of the email you did a REPLY to that does not pertain to your question. It tends to confuse the issue. Next, I am not clear on Reading a VS on JES2 Spool. JES2 Spool has its own unique process for creating SYSOUT. So if you could explain further that could

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

If these are Linklst'd datasets, then you could 1) Build a new LINKLST and remove these datasets in the new LINKLST 2) Do what you need to with these files (move, delete) 3) then if you need them back, build a new copy of the linklst Everything will depend on what these datasets are and

IEC141I 013-A8: how to read VS data sets?

One of our apps abends if trying to read a VS data set on the JES2 spool. The message manual tells me this is because it is not allowed to read VS SYSOUT using QSAM. Yet we have another application which does exactly that. Furthermore, after one day of staring at the code I cannot see any

Re: CLOCKxx - ACCURACY Parameter - IEA032E message

Glenn, Now I don't know your exact setup but this is what I have seen. I don't use the accuracy parameter. I don't see why the STP needs to be using an external time source directly to be accurate. NTP is a nifty protocol that takes latency into account right back to the root of the chain

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

Lucas Rosalen wrote: >You could do the right way, which means removing these datasets from LLA and >LNKLST. Agreed! >Or you could recklessly use BYPASSNQ program, which can be found in CBT file >#749 Hehehe, 'recklessly'? That AC(1) program is a frontend to screen SVCs and then misuse

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

You could do the right way, which means removing these datasets from LLA and LNKLST. Or you could recklessly use BYPASSNQ program, which can be found in CBT file #749 ---

Re: Delete NVR entries where ENQ shows from LLA/XCFAS

Ravi Gaur wrote: >Delete datasets from Disk/3390 which are having enqueue from LLA/XCFAS >Tried IDCAMS NVR and also ISPF 3.2 (with VOLUME serial no.) get in use >message any trick to get the datasets deleted via bypassing enqueue? on this >specific volume Are those datasets cataloged with

Delete NVR entries where ENQ shows from LLA/XCFAS

Delete datasets from Disk/3390 which are having enqueue from LLA/XCFAS Tried IDCAMS NVR and also ISPF 3.2 (with VOLUME serial no.) get in use message any trick to get the datasets deleted via bypassing enqueue? on this specific volume