Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - J9CMOD

Pages: [1] 2 3
1
z/OS Server / Re: Contents of data in the CMOD.MIGR.BANNER.INPUT file
« on: January 14, 2018, 05:49:31 PM »
Thanks Nolan.  I am nose-deep in some other issues currently, but I will read the manual you supplied, and let you know if I come up with a solution that includes your challenge.

2
z/OS Server / Need page break on non-carriage-control character
« on: January 12, 2018, 01:34:23 PM »
We have some documents that I can't get to load correctly.  Here's is the info that impacts this:
-  They do NOT have carriage control, and we don't want carriage control added.
-  The "new page" should always start when it finds an X in column 1
-  Column 1 is used for data and must print as part of the data.
-  We use Indexer: OS/390
-  RECFM = Fixed
-  LRECL = 133
-  DATA TYPE is Line  (They're line data output from cobol programs)
-  I can't use the line count, because there could be a different number of lines from one page to the next.  NOTE: Although I can't use the linecount,  I tried that and found that it showed the correct number of pages within the view (if they were the same size), but it didn't show the correct number of pages in the page count in the list of results.

Do you know how to make this happen?  I have tried many combinations, using INDEXSTYLEs DOC and NODX.

Here is what I have coded currently, that doesn't break the pages based on the X.  NOTE:  The inpexit is one we have created.  If I don't include the input exit, it doesn't load at all.  If I use the "out-of-the-box" ARSEXINP, it abends ARSLOAD.

CC=NO
CONVERT=NO
CPGID=500
FILEFORMAT=RECORD,133
GROUPMAXPAGES=9999
INDEXOBJ=ALL
INDEXSTARTBY=0
INDEXSTYLE=NODX   
INPEXIT=CMDEXINP    /* This is an input exit that will add carriage control every 65 lines if it doesn't find it, if CC=YES */
TRIGGER1=*,1,'X',(TYPE=GROUP)   
FIELD1=0,1,8,(TRIGGER=2,BASE=0)
INDEX1='SEGMENT_NUMBER',FIELD1,(TYPE=GROUP,BREAK=YES)
INDEX2='REPORT_DATE',FIELD1,(TYPE=GROUP,BREAK=YES)
INDEX3='PAGE_NO',FIELD1,(TYPE=GROUPPAGE,BREAK=YES)
LINECNT=16
CCTYPE=A   /*  This automatically gets added by the system if I don't code it */

3
Thanks Ed,
We still get that error, and I don't see any upgrades in our near future.  Thanks for the info!

4
z/OS Server / Re: Contents of data in the CMOD.MIGR.BANNER.INPUT file
« on: January 12, 2018, 06:39:30 AM »
I don't have a lot of info on that exit, so I haven't tried to change it/use it in any specific ways.  Can you expand on what I would need to do to make this happen?

5
z/OS Server / Re: ars.cfg parms for manifest
« on: November 09, 2017, 11:37:58 AM »
Hate to admit this a little, but I was misunderstanding the documentation.
Two areas I didn't understand:
   When I read that the new parm was created to allow bundles to be in separate spool files, or one, like manifest, I thought that meant there was a parm for manifest.
   When I saw the choices of manifest, no manifest, and manifest in sysout, I jumped to the conclusion that maninfest in sysout meant it would sit out in the sysout queue to view and not be printed.

So - solution is - just choose manifest in sysout.

I'm testing it tonight to see if that's enough to allow QDirect to keep it together, without changing the dynamic creation of the DD name for the output.

Just wanted to answer this to save somebody else the headache.

6
Ed,
Here's the info from my ETS resource:
The ARS address spaces have 1.54G private area
, the OMVS segment for ARSSERVR already says ASSIZEMAX= 2147483647, which canít raise that 1.5 number but at least he can see it isnít lowering it.

Does that answer your questions/curiosity?

Thanks,
J9

7
z/OS Server / ars.cfg parms for manifest
« on: November 08, 2017, 01:40:01 PM »
I've read manuals, programs, parms and copybooks and can't find the answer, so I'm hoping somebody can help here.
We recently started using manifests for several distributions.  The problem is that the manifest produces with a different DD name from the other output in the bundle, which causes issues when it is sent to our Print Product.
It looks like you can set a parm somewhere.  Can anybody tell me how to force the manifest to print with the same DD name(s) as the rest of the output for the bundles?
Currently, each piece of the bundle goes out to the spool with DD names that start with P, and the manifest goes out to the spool with a DD name that starts with M - I need the manifest to be "considered the next P.  (NOTE - It does keep all the output in the same spool job)
For example, I have a Distribution with 3 Report Bundles and a manifest.  It goes to the spool with the following DD names:
P0000001  (1st application)
P0000002  (2nd application)
P0000003  (3rd application)
M0000003 (manifest)


I need the manifest to go to the spool as part of the bundle, which would cause it to have the following DD names:
P0000001  (1st application)
P0000002  (2nd application)
P0000003  (3rd application)
P0000004 (manifest)

8
I set up the job to run, but it has to be run by our ETS department, I'll let you know about the results.

9
It's set to 30.  I can talk to our OAM Team to see if we can make it higher, if you think that will help.  That number came from our Health Check, but we've grown since then in our CMOD usage.

10
We randomly get the error ARS0131E ZCMOD01P No logical place to retrieve object  during distributions.  Normally, CMOD appears to correct itself and distribute correctly.  However, we recently had over 4000 of those errors during one nightly cycle, and the output was never distributed.
We researched and it appears that an incorrect, or empty, Storage Set is being set to OAM.  Since we have all of our Storage Sets correctly set up, we don't know what causes this.
Has anybody encountered and fixed this issue?
Is there a default "backup" storage set we should have set in one of our parms that we don't know about?

Any assistance would be greatly appreciated.

Thanks,
Janine

11
z/OS Server / Re: Contents of data in the CMOD.MIGR.BANNER.INPUT file
« on: October 12, 2017, 07:01:02 AM »
I still haven't found the solution to this issue.  I've tried several things, and one of my co-workers said somebody at IBM said this was not possible.  I know the manifest will print all the reports in the bundle, so I think there is probably a way to do it in the banner exit also.   We use the banner exit, but I did see this comment (in ARSRBANO) and wondered if it was removed from both programs:

7/25/2014 14206  1.1.2 Support multiple banner names in   
                       ODSBAN.  This used to be supported.
                       Where did it go?                   
                                                         
Any ideas?
Thanks!
Janine
 

12
z/OS Server / Contents of data in the CMOD.MIGR.BANNER.INPUT file
« on: June 19, 2017, 09:42:24 AM »
We are using CMOD Banners in the BANNER.INPUT file in CMOD instead of manifests, because of specific needs of the software (and department) we are sending our print to. 
However, as part of the data in the banner, we need to list all the ReportIDs in the bundle, all the Bundle IDs and/or all the Distribution IDs.  Since all the Report IDs are listed in the manifest, it seems that the data is available.  However, I can only find a way to get ONE of each listed in the banner - we use OD_RID, BID, and DID.
Does anybody know how I can get it to list ALL the RIDs, BIDs and DIDs on the banner?

13
z/OS Server / ARSODF DRT, DST, & PPT Status
« on: January 04, 2017, 12:51:15 PM »
I've looked in the manuals, and through the postings here, but can't find it.
Can anybody tell me where I can find the meaning of the Status in the ODF Tables DRT, DST, & PPT (EX: 16 = complete)?
Thanks
J9

14
Thanks Claudio.
I actually went that direction in November, and am in the process of getting it into Production.
I left this open in case somebody had a better idea, so I didn't have to add another set of jobs to our nightly cycle, but the External with the job to release is actually working out very well.

15
To accomplish this need in SAR, we had them bundled, and used a time delay that was sufficient to make sure all reports that would be created had enough time run before the bundle was processed.
Here are the attributes as they are shown in SAR (where we set up bundle attributes).  If I could set the same attributes in CMOD, it would work for me.
Attributes:                                                         
  Banner   ===> ( MFB9790  , *        , *        )                 
  BDist    ===> CBO-EP1-J                                           
  Late     ===>                    Bundle Confirm?   ===>           
  Interval ===> 00:10              Wait (Int, Late)  ===> ( Y , N )

Pages: [1] 2 3