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 - Greg Ira

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 ... 16
91
MP Server / Re: OS390 indexer
« on: January 12, 2017, 08:56:25 AM »
Correct.  If host, install directories, and other information changes you will need to modify those ars.ini files.
Just to reiterate.  The name resolved by the -h parm in your proc should match the name specified in the @SRV@ line of the ars.ini on the mainframe.  You have a lot of version names in your paths as well.  Make sure you note which, if any, of those change when you upgrade and modify those paths accordingly in all your config files and JCL.

92
MP Server / Re: OS390 indexer
« on: January 12, 2017, 08:26:38 AM »
If the server name changes you will need to make a change to the PODA30SR PROC or any other similar PROC that is used to load documents by modifying the H=cccccccc parm in the proc.
If you are upgrading you will/should likely change the CMOD= parm to point to the new loadlib HLQ (eg SYS1.ONDEMAND.V95)
In the proc you will also need to change the path of the ARSBIN to match the new install path.

You will also need to change ars.ini if the IP address, host name, or server name changes.

93
MP Server / Re: OS390 indexer
« on: January 12, 2017, 07:38:34 AM »
That helps a lot.
Based on this job you are basically loading from a dataset instead of a directory.

In step ODA30S20 you are taking the input dataset and sorting it into a temporary dataset "&&RPTDSN"
Step ODA30S25 is running ARSLOAD using the temp dataset created in step above as the input dataset:  "-s IN1"
 (You see IN1   DD DSN=&&RPTDSN in JCL later)

This gets loaded to your server DPYCSERR ("-h &H"  which points to H=DPYCSERR earlier in the proc)
And to the application defined in the calling job RPTID=GSP36201  (-a &RPTID)

Does this clear it up any for you?


94
MP Server / Re: OS390 indexer
« on: January 12, 2017, 06:22:14 AM »
Quote
We have JCL for loading OS390 reports to PROD.
Can you post that JCL?  That would help

95
MP Server / Re: OS390 indexer
« on: January 11, 2017, 12:41:30 PM »
OS390 does use ARSLOAD as well.  Same as ACIF.

96
MP Server / Re: OS390 indexer
« on: January 11, 2017, 08:48:20 AM »
Can you give us a little more information such as what type of mainframe?
On our z/OS IBM Mainframe the output is dropped onto the JES spool where there is an ARSLOAD started task that monitors the spool and loads anything meeting the load definitions.  To me it sounds like this is what's happening with your output.

97
Report Indexing / Re: Using RMS/SDSF "?" Functionality in CMOD
« on: December 06, 2016, 01:36:37 PM »
This is part of ARSYSPIN.  A Job loaded through ARSYSPIN will come out as a single document with each beginning and ending separator record on their own page within the document.
Something like:
Page 1:  "B        O#32AOD2-JOB20607 JES2    JESMSGLG...."
Page 2:  JES JOB LOG
Page 3:  "E        O#32AOD2-JOB20607 JES2    JESMSGLG..."
Page 4:  "B        O#32AOD2-JOB20607  JES2    JESJCL....."
Page 5:  JES JCL
....


The header records are generated automatically from the DD names, no JCL changes necessary.  That's one of the big benefits of use ARSYSPIN.  It handles JES formats and spool datasets for you.

98
Report Indexing / Re: Using RMS/SDSF "?" Functionality in CMOD
« on: December 06, 2016, 06:42:11 AM »
I have found a slightly clunky way to replicate the ? functionality with jobs stored using ARSYSPIN.  As long as you have separator records being generated (OUTSEP=YES) you can use the search function to simulate ?.
The records look like this:
B        O#32AOD2-JOB20607        JES2    JESMSGLGP1OFT   STD     CTW1C.O#32AOD2.JOB20607.D0000002.JESMSGLG    2016-12-0608.30.00.5600152016-12-0608.30.00.56

B marks the beginning of the step.  E marks the end.  If you copy the first section of the record(B        O#32AOD2-JOB20607), paste it into search, do a find all you end up with the following list.  Double clicking the entry will allow you to jump to that step:
B        O#32AOD2-JOB20607        JES2    JESMSGLGP1OFT
B        O#32AOD2-JOB20607        JES2    JESJCL  P1OFT
B        O#32AOD2-JOB20607        JES2    JESYSMSGP1OFT
B        O#32AOD2-JOB20607        STAT03  SYSOUT  P1OFT
B        O#32AOD2-JOB20607        GENDTE03SYSTSPRTP1OFT
B        O#32AOD2-JOB20607        GENRPT03SYSOUT  P1OFT
B        O#32AOD2-JOB20607        STAT05  SYSOUT  P1OFT
B        O#32AOD2-JOB20607        GENDTE05SYSTSPRTP1OFT
B        O#32AOD2-JOB20607        GENRPT05SYSOUT  P1OFT
B        O#32AOD2-JOB20607        STAT14  SYSOUT  P1OFT
B        O#32AOD2-JOB20607        GENDTE14SYSTSPRTP1OFT
B        O#32AOD2-JOB20607        GENRPT14SYSOUT  P1OFT
B        O#32AOD2-JOB20607        STAT23  SYSOUT  P1OFT
B        O#32AOD2-JOB20607        GENDTE23SYSTSPRTP1OFT
B        O#32AOD2-JOB20607        GENRPT23SYSOUT  P1OFT
B        O#32AOD2-JOB20607        STAT25  SYSOUT  P1OFT
B        O#32AOD2-JOB20607        GENDTE25SYSTSPRTP1OFT
B        O#32AOD2-JOB20607        GENRPT25SYSOUT  P1OFT


Not the most elegant solution but if you have a job with many steps it can help.

99
z/OS Server / Re: Extracting Resources
« on: November 30, 2016, 12:09:34 PM »
If I had to venture a guess you would need to extract the resource separately from the document using the resource object name.
Something like:
 arsadmin retrieve -g somegrp -h archive -m 2 -n123-0 -d /etc/temp -u user -p passwrd 2 3

Which should retrieve resources 2 & 3 for application group somegrp.

100
I tried a number of different things to recreate this.  The only way I could get it to act similarly was to define and save the AG without the segment then open the AG for update and add a date field.  It looks like once the AG is saved without a segment defined it can't be added after the fact.

101
There isn't a specific action that would enable the segment field to be avialable.  If there are no other fields selected as segment and the current field is in date format then segment should be available to you.  It sounds to me like something else is amiss in your environment though what that could be escapes me at the moment. 

102
z/OS Server / Re: Trying to replace ARSZOSHL with oshell
« on: October 25, 2016, 08:19:51 AM »
"10/25/16 09:05:12 : Connection cannot be established for the cpua.tjx.com server" is likely the key to the issue.

Check the .profile for the userid that's running the job's and be sure it's has the correct paths, steplibs and DSNAOINI.

103
z/OS Server / Re: How to make fallback from upgrade?
« on: October 19, 2016, 05:37:59 AM »
Truthfully I can't remember the exact reason we created the command then ran them in a separate step.  I think we were running into issues when trying to run the various commands using the PARM='SH..' parameter of BPXBATCH so we just went the "easy" route.

104
z/OS Server / Re: How to make fallback from upgrade?
« on: October 14, 2016, 10:42:57 AM »
Hi Marthin,
  We do our fallback a bit different.  We've run a restore this way probably about a dozen times with no real issues.
 We unload the cmod tables to a backup directory and if we need to fall back we drop the tables and recreate them with the previous version and loading from the backups.

This is the JCL we use to unload the pre upgrade tables:
//**************************************************************
//* This job is used to back up all CMOD tables (14P) AT 8.5.
//* this is done as part of the fallback process.
//**************************************************************
//**************************************************************
//*  Copy statement to UNLOAD CMOD tables prior to migration
//**************************************************************
//CPYLOAD  EXEC PGM=IKJEFT01,COND=(4,LT)
//OUTHFS   DD PATH='/etc/ond/14P/temp/upgd95.cmd',
//            PATHDISP=(KEEP,DELETE)
//INMVS    DD *
cd /SYSTEM/etc/ond/14P/backup/
/usr/lpp/ars/V8R5M0/bin/arsdb -I ond14P -vx
/*
//SYSTSPRT DD SYSOUT=(,)
//SYSTSIN  DD *
OCOPY INDD(INMVS) OUTDD(OUTHFS) TEXT CONVERT(YES) PATHOPTS(USE)
/*
//*
//**************************************************************
//*    Run the command created in previous step
//**************************************************************
//RNLOAD  EXEC PGM=BPXBATCH,REGION=0M,COND=(4,LT)
//STEPLIB DD DSN=ONDDODP.V10.SDSNEXIT,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOAD,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOD2,DISP=SHR
//STDIN  DD PATH='/etc/ond/14P/temp/upgd95.cmd',PATHOPTS=(ORDONLY)
//SYSOUT DD SYSOUT=(,)
//SYSERR DD SYSOUT=(,)
//STDOUT DD SYSOUT=(,)
//*

The following JCL would fallback to 8.5 from 9.5:

//**************************************************************
//* This job is used to fall back a CMOD instance (14P) to 8.5.
//* This is accomplished in 3 steps:
//* 1) Deleting all system tables under the upgraded release.
//* 2) Re-Create all system tables.
//* 3) Restore the CMOD Table Data from unloaded tables.
//**************************************************************
//**
//**************************************************************
//*     Delete all CMOD tables with prompt of "Y" in STDIN.
//**************************************************************
//DELSYS  EXEC PGM=BPXBATCH,REGION=0M,COND=(4,LT),
//       PARM='SH /usr/lpp/ars/V9R5M0/bin/arsdb -I ond14P -vd'
//STEPLIB DD DSN=ONDDODP.V10.SDSNEXIT,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOAD,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOD2,DISP=SHR
//STDIN  DD PATH='/SYSTEM/etc/ond/responseyes.txt', <= Reply to DELETE
//          PATHOPTS=(ORDONLY)
//SYSOUT DD SYSOUT=(,)
//SYSERR DD SYSOUT=(,)
//STDOUT DD SYSOUT=(,)
//**
//**************************************************************
//*    Copy statement to Create/Build CMOD System tables.
//**************************************************************
//CPYCRT   EXEC PGM=IKJEFT01,COND=(4,LT)
//OUTHFS   DD PATH='/etc/ond/14P/temp/upgd85.cmd',
//            PATHDISP=(KEEP,DELETE)
//INMVS    DD *
cd /etc/ond/14P/temp/
/usr/lpp/ars/V8R5M0/bin/arsdb -I ond14P -vrt -O
/*
//SYSTSPRT DD SYSOUT=(,)
//SYSTSIN  DD *
OCOPY INDD(INMVS) OUTDD(OUTHFS) TEXT CONVERT(YES) PATHOPTS(USE)
/*
//*
//**************************************************************
//*    Run command created in previous step
//**************************************************************
//RNCREAT EXEC PGM=BPXBATCH,REGION=0M,COND=(4,LT)
//STEPLIB DD DSN=ONDDODP.V10.SDSNEXIT,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOAD,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOD2,DISP=SHR
//STDIN  DD PATH='/etc/ond/14P/temp/upgd85.cmd',PATHOPTS=(ORDONLY)
//SYSOUT DD SYSOUT=(,)
//SYSERR DD SYSOUT=(,)
//STDOUT DD SYSOUT=(,)
//*
//**************************************************************
//*    Copy statement to Load from backups.
//**************************************************************
//CPYLOAD  EXEC PGM=IKJEFT01,COND=(4,LT)
//OUTHFS   DD PATH='/etc/ond/14P/temp/upgd85.cmd',
//            PATHDISP=(KEEP,DELETE)
//INMVS    DD *
cd /etc/ond/14P/backup/
/usr/lpp/ars/V8R5M0/bin/arsdb -I ond14P -vi
/*
//SYSTSPRT DD SYSOUT=(,)
//SYSTSIN  DD *
OCOPY INDD(INMVS) OUTDD(OUTHFS) TEXT CONVERT(YES) PATHOPTS(USE)
/*
//*
//**************************************************************
//*    Run command created in previous step
//**************************************************************
//RNLOAD  EXEC PGM=BPXBATCH,REGION=0M,COND=(4,LT)
//STEPLIB DD DSN=ONDDODP.V10.SDSNEXIT,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOAD,DISP=SHR
//        DD DSN=ONDDODP.V10.SDSNLOD2,DISP=SHR
//STDIN  DD PATH='/etc/ond/14P/temp/upgd85.cmd',PATHOPTS=(ORDONLY)
//SYSOUT DD SYSOUT=(,)
//SYSERR DD SYSOUT=(,)
//STDOUT DD SYSOUT=(,)
//*

This has worked pretty well for us but I suggest running through it with a test instance a number of times to get comfortable with it.

105
Other / Re: AFP view failing- T1GMCUSR code page is not found
« on: October 06, 2016, 06:24:23 AM »
I'm definitely not a font mapping expert but we've run into this issue frequently with one customer who likes to create their own fonts.
What we've done is basically identify a suitable PC based font that matches, or closely matches, the actual font.
This we add a FGID for if there isn't one (csdef.fnt  near bottom of file)
 eg.  3840=Arial,Modern,MED,0

Next we add the charset (top of csdef.fnt)
 eg.   C?AR08NP=3840,80,73,0,0

? is a wildcard.  This will use the Arial FGID to represent the font with height of 80, width of 73, no strikeover and no underline.  Again we've had to play with height and width to get the font to look correctly on the form.

As for code page (cpdef.fnt) we've only had to define three of those.
Two were easy by simply defining it to use the code page id of 37.  eg T1OMNI=37,ANSI 

The third code page was a nightmare as I had to find the nearest matching code page using the old *.cp files that used to come with the clients then write an output exit that changed the remaining codes that didn't match to match those in the code page.

My suggestion would be to start with TIGMCUSR=37,ANSI in cpdef.fnt and then work with csdef.fnt definitions to get it to display correctly.

Hope this helps a bit.

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 ... 16