Quantcast
Channel: IBM Mainframe Computers Forums
Viewing all 8500 articles
Browse latest View live

IMS DB/DC :: RE: IMS Database backup info

$
0
0
Author: Gary Jacek
Posted: Sun Nov 20, 2016 11:26 am (GMT 5.5)

Correct, the DBRC API does not support LIST.

However it does support for example, QUERY TYPE=DB as well as other query types.

That said, I would still expect my job scheduling subsystem (ESP, Control-M...) to tag failed Image Copy jobs for attention.


Suggestions & Feedback :: RE: Modifying the ban on diiscussing symbolic parms instream?

$
0
0
Author: Bill Woodger
Subject: Reply to: Modifying the ban on diiscussing symbolic parms instream?
Posted: Sun Nov 20, 2016 1:56 pm (GMT 5.5)

On reading your initial post on the topic, it didn't require brain science or discussion, just an edit button.

I have assumed that you checked all the other rules. Nothing about "changing RC in a JOB"?

We await a new avalanche of questions on the topic of symbols with increased flexibility in JCL, as the news spreads rapidly from continent to continent with each sunrise on 20 November 2016.

Suggestions & Feedback :: RE: Modifying the ban on diiscussing symbolic parms instream?

$
0
0
Author: jasorn
Posted: Sun Nov 20, 2016 3:21 pm (GMT 5.5)

Yeah, I missed that. There's been enough changes lately, perhaps there should be a 'Changes' sticky that's updated for each release that points changes out for those who miss reading the change log or don't quite understand the changes.

If that's already happening, I've been missing those posts.

Did I mention I love this forum? Best work related site ever.

JCL & VSAM :: RE: FTP - JCL failed while passing FTP commands in dataset

$
0
0
Author: jasorn
Posted: Mon Nov 21, 2016 2:47 am (GMT 5.5)

Suneetha1612
You do not mention that you've compared the output, aka '//OUTPUT DD SYSOUT=*', from both the working and non working after putting debugging statements in. And the same for the INPUT commands. In my experience(far less than 7,500 replies), this will almost certainly show you exactly what is wrong with your input commands.

And, trust me, these people are here to help. They've helped me so much.

JCL & VSAM :: RE: ERROR WHILE SUBMITTING LOAD JOB

$
0
0
Author: jasorn
Subject: Re: Reply to: ERROR WHILE SUBMITTING LOAD JOB
Posted: Mon Nov 21, 2016 3:04 am (GMT 5.5)

We have to do this in two jobs in my shop. In my experience the setup for this varies from shop to shop. It seems to me your team should know these answers or you should meet with your support staff to get an understanding of how things are set up there.

ANURADHA NEELAKANTAN wrote:

Here I am facing a problem like, unable to unload(prod region) and load (dev region) using this single MAIN statement. Is there any way can I do it both in one jcl?

JCL & VSAM :: Updating the counters after eliminating duplicates

$
0
0
Author: PANDU1
Subject: Updating the counters after eliminating duplicates
Posted: Mon Nov 21, 2016 9:47 am (GMT 5.5)

Hi Everyone,

Can any one suggest me in solving this query,

If my input file is

Code:
01 HEADER1
05 RAMU      85870         
05 RAJESH    85871       
05 RAMU      85870         
05 SOMU      85878       
05 RAJU      85890       
05 RAMU      85870         
05 AKIL      85889     
99 COUNT1 - 7
01 HEADER2
05 RAMU      85850         
05 RAJESH    85851       
05 RAMU      85852         
05 SOMU      85858       
05 RAJU      85850       
05 RAMU      85851         
05 AKIL      85850     
99 COUNT2 - 7

And my output with - updated the counts of individual header after eliminating duplicates in employee number. i.e.
output file:

Code:
01 HEADER1
05 RAMU      85870         
05 RAJESH    85871       
05 SOMU      85878       
05 RAJU      85890       
05 AKIL      85889     
99 COUNT1 - 5
01 HEADER2
05 RAMU      85850         
05 RAJESH    85851       
05 RAMU      85852         
05 SOMU      85858       
99 COUNT2 - 4


Which sort utility can be used for this and how?

code' d

JCL & VSAM :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: Arun Raj
Posted: Mon Nov 21, 2016 11:15 am (GMT 5.5)

PANDU1,

Welcome to the forums! You should probably be able to achieve this with whichever sort product is available at your site (DFSORT, Syncsort,..).

Search the DFSORT forum here for examples on how to "remove duplicate"s or creating "trailer count"s.
Try something and get back if you face any issues. Someone would be here to help. Good luck!

Also make sure you include all the relevant information, RECFM, LRECL, field positions of your actual data, sort order of the input data (if any), sort order of the output (if it matters). Post code/sample data using "Code" tags.
_________________
Arun
----------------------------------------------------------------------------------------------------
Love is like an hourglass, with the heart filling up as the brain empties. -Jules Renard

JCL & VSAM :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: enrico-sorichetti
Subject: Reply to: Updating the counters after eliminating duplicates
Posted: Mon Nov 21, 2016 12:17 pm (GMT 5.5)

tell us what sort product You will be using.

look at the messages

WER... ==> SYNCSORT
ICE... ==> IBM DFSORT

and the topic will be moved to the proper section
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif


JCL & VSAM :: Limit duplicate records in the SORT

$
0
0
Author: pshongal
Subject: Limit duplicate records in the SORT
Posted: Mon Nov 21, 2016 12:54 pm (GMT 5.5)

Hi All,
I have a requirement to limit number of duplicate records in a file.

For e.g:
Below is the record pattern

Code:
AAA
AAA
BBB
BBB
BBB
BBB
CCC
CCC
CCC
DDD

Requirement is to have max 2 duplicate records. So my o/p should be

Code:
AAA
AAA
BBB
BBB
CCC
CCC
DDD

Thanks.
_________________
Thanks,
PS

JCL & VSAM :: RE: Limit duplicate records in the SORT

$
0
0
Author: enrico-sorichetti
Subject: Reply to: Limit duplicate records in the SORT
Posted: Mon Nov 21, 2016 1:03 pm (GMT 5.5)

tell us what sort product You will be using.

look at the messages

WER... ==> SYNCSORT
ICE... ==> IBM DFSORT

and the topic will be moved to the proper section
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif

JCL & VSAM :: RE: Limit duplicate records in the SORT

$
0
0
Author: pshongal
Posted: Mon Nov 21, 2016 1:06 pm (GMT 5.5)

We use SYNCSORT
_________________
Thanks,
PS

SYNCSORT :: RE: Limit duplicate records in the SORT

$
0
0
Author: Pandora-Box
Posted: Mon Nov 21, 2016 2:09 pm (GMT 5.5)

Use WHEN=GROUP
_________________
To understand recursion, You must understand recursion
Pandora icon_smile.gif

SYNCSORT :: RE: Limit duplicate records in the SORT

$
0
0
Author: Bill Woodger
Subject: Reply to: Limit duplicate records in the SORT
Posted: Mon Nov 21, 2016 2:22 pm (GMT 5.5)

Assuming your data is in key order, extend record temporarily with a sequence number, with RESTART= for the key, and out OUTFIL with INCLLUDE=/OMIT= to do the limiting, with BUILD to drop off the extension.

The same could be achieved with WHEN=GROUP, but if the key is on each record, in the same position, then it is better to use the plain sequence number.

SYNCSORT :: RE: Limit duplicate records in the SORT

$
0
0
Author: pshongal
Subject: Reply to: Limit duplicate records in the SORT
Posted: Mon Nov 21, 2016 3:50 pm (GMT 5.5)

Hi Bill,

Yes, its in sorted order and key is always in same position.
_________________
Thanks,
PS

SYNCSORT :: RE: Limit duplicate records in the SORT

$
0
0
Author: pshongal
Posted: Mon Nov 21, 2016 4:01 pm (GMT 5.5)

Thanks Bill & Pandora for your suggestion.

I used sequence number technique. It works. Thanks a lot
_________________
Thanks,
PS


DFSORT/ICETOOL :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: PANDU1
Posted: Mon Nov 21, 2016 5:27 pm (GMT 5.5)

Thanks Arun Raj and enrico-sorichetti

Field positions are as follows

01-2 - Sequence number
04-10 - Employee name
12-5 - Employee number(sort field)

Let the RECFM and LRECL valued be FB & 30 respectively.

DFSORT/ICETOOL :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: Rohit Umarjikar
Posted: Mon Nov 21, 2016 9:23 pm (GMT 5.5)

Code:
//SYSIN    DD *                                                       
  INREC IFTHEN=(WHEN=GROUP,BEGIN=(4,6,CH,EQ,C'HEADER',OR,4,4,CH,EQ,   
                                            C'COUNT'),PUSH=(81:ID=8)),
  IFTHEN=(WHEN=(4,6,CH,NE,C'HEADER'),OVERLAY=(89:1,10)),             
  IFTHEN=(WHEN=(4,5,CH,NE,C'COUNT'),OVERLAY=(89:1,10))               
  SORT FIELDS=(81,18,CH,A),EQUALS                                     
  SUM FIELDS=NONE                                                     
  OUTREC BUILD=(1,30)     

Though, you will find a way to update COUNT by doing little research.
_________________
Regards,
Rohit Umarjikar
"Knowledge is knowing that a tomato is a fruit, but Wisdom is knowing not to put it in a fruit salad."icon_razz.gif

DFSORT/ICETOOL :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: Bill Woodger
Subject: Reply to: Updating the counters after eliminating duplicates
Posted: Mon Nov 21, 2016 10:54 pm (GMT 5.5)

No, Rohit.

Even accepting the 4.4 comparison for C'COUNT' as a typo, you don't want to use HEADER and COUNT, for your tests, as there is absolutely nothing to stop these giving you a "false hit" if they happen to occur in at that position in a name.

There are clearly indicators for the header and trailer which give no possibility of a false hit. There is also, clearly, a "reference number" which should be used for the sort/deduplication, even if that is not sufficient (no indication) there is no reason to includ the "05" or the blank following it or only a selected part of the name field.

WHEN=GROUP with BEGIN for "01", END for "99". Sort field after the ID to contain X'00' for header, X'FF' for trailer.

To suggest using COUNT, you can't chop off the extension in OUTREC.

A sequence, with RESTART for the ID extension and an IFTHEN=(WHEN=(logcicalespression) on OUTREC would allow a JFY with SHIFT=LEFT for the format of count shown.

DFSORT/ICETOOL :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: Arun Raj
Posted: Tue Nov 22, 2016 11:09 am (GMT 5.5)

I think we are good without an END for the group.
This is UNTESTED, this has the essence of Bill's suggestion above.
Code:
//SYSIN    DD *                                                       
  INREC IFTHEN=(WHEN=GROUP,BEGIN=(1,2,CH,EQ,C'01'),   
                           PUSH=(81:ID=8)),
  IFTHEN=(WHEN=(1,2,CH,EQ,C'01'),OVERLAY=(89:5X'00')),             
  IFTHEN=(WHEN=(1,2,CH,EQ,C'99'),OVERLAY=(89:5X'FF')),             
  IFTHEN=(WHEN=NONE,OVERLAY=(89:14,5))
             
  SORT FIELDS=(81,13,CH,A)
  SUM FIELDS=NONE                                                   
  OUTREC IFTHEN=(WHEN=INIT,OVERLAY=(89:SEQNUM,5,ZD,RESTART=(81,8))),
         IFTHEN=(WHEN=(1,2,CH,EQ,C'99'),
         OVERLAY=(89:89,5,ZD,SUB,+2,ZD,M10,LENGTH=5,
                  13:89,5,JFY=(SHIFT=LEFT)),
  IFOUTLEN=30

_________________
Arun
----------------------------------------------------------------------------------------------------
Love is like an hourglass, with the heart filling up as the brain empties. -Jules Renard

DFSORT/ICETOOL :: RE: Updating the counters after eliminating duplicates

$
0
0
Author: Bill Woodger
Subject: Reply to: Updating the counters after eliminating duplicates
Posted: Tue Nov 22, 2016 2:43 pm (GMT 5.5)

Yes, Arun, that looks good. I got confused with the END because the trailer was being treated as a separate group by Rohit :-)

I'd rearrange the order of the IFTHENs, so that the data-one is treated first, it'll avoid a lot of tests for when the header/trailer when most of the records will be data. Multiple IFTHEN=(WHEN=(logicalexpression) are like an EVALUATE in COBOL, so cease the processing of that construct as soon as there is a "hit". That behaviour can be modified, when needed (for two entirely independent operations on the same record) by using HIT=NEXT.

Viewing all 8500 articles
Browse latest View live