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 - Nolan

Pages: 1 2 3 4 5 6 [7] 8 9 10
91
MP Server / Re: CMOD at V9.0 End Of Service September 30th, 2017
« on: September 07, 2017, 07:51:09 AM »
We needed FP V9.5.0.9 MP to resolve a PDF Indexer issue.   On target to complete migrations to V9.5.0.8 on Z/OS  ::)

92
z/OS Server / Re: Upgrading to Version 9.5 and Monarch Intergration
« on: September 07, 2017, 07:44:22 AM »
We had a PMR around using arsole.ocx accessing large object documents.  Ensure you have updated the desktop client to a version higher than V9.5.0.2, that was required to resolve the issue. 

Cheers

93
z/OS Server / Re: Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5
« on: July 26, 2017, 06:58:12 AM »
RESOLVED  :D

Details not included in the readme or anywhere else I looked.

To continue using the Report Specification Exit in COBOL with out modifications you must do the following steps.

1. Recompile the exit as per usual with any release
2. Create a directory in OMVS to hold customer exits.  Example: /usr/lpp/ars/V9R5M0/custom/exits
3. Update ars.cfg with path name of custom exits.  Example: ARS_USER_EXITS_DIR=/usr/lpp/ars/V9R5M0/custom/exits
4. Update and run SARSINST(ARSUUPDJ).  Ensure you point the hfs file to the same path used above.  Example:  /usr/lpp/ars/V9R5M0/custom/exits
     Note you do not need to modify SARSINST(ARSUUPDC)

WARNING.  You need to use your custom path for other exits.
For Security Exit we had to use two of the stock samples
SARSINST(ARSUSECX) - Customized for our needs
SARSINST(ARSUSEJJ) - Stock IBM SARSINST(ARSUSECC)
SARSINST(ARSUPERJ) - Stock IBM SARSINST(ARSUPERC) - required if using security exit apparently.

For Banner Exit
SARSINST(ARSCODFX) - Stock IBM SARSINST(ARSODFXA)
SARSINST(ARSCODFX)  - We Modified SARSINST(ARSODFXB) to our needs
SARSINST(ARSCODFX) - Stock IBM SARSINST(ARSODFXM)


Hopefully, this will save someone a few headaches   ::)

94
The ODSCRT table is outside of the OnDemand product, it was probably supplied by the services team.  It is a basic DB/2 table for us that we use REXX scripts to update/insert/change.  You can insert the details using any of your preferred methods to maintain the table.  We also use the DSNUTILB DB/2 batch load tool to do bulk loading.


95
MP Server / Re: Adding PPD's to a PDF file
« on: May 17, 2017, 08:30:33 AM »
The LAB file with detailed commands and examples is over the 5MB limit allowed on the message board.  PM your email address and I will send direct.

We did try in-house and it worked successfully.



96
MP Server / Re: Adding PPD's to a PDF file
« on: May 17, 2017, 08:25:36 AM »
Bud Paton presented using arspdoci and all other forms of using PDF indexing.  See attached

97
z/OS Server / Re: Converting ARSBDIST to new ARSODF options
« on: April 17, 2017, 01:53:59 PM »
I don't think the -ef is valid anymore.   It looks like all you need is -e

arsodf -I instancename -e -d 'Daily sales invoices' -r ASMITH

https://www.ibm.com/support/knowledgecenter/en/SSQHWE_9.5.0/com.ibm.ondemand.odf.doc/doddf329.htm

And I won't ask why Ed is not using a stash file :p





98
z/OS Server / Cobol ARSUUPDZ and ODSXUPDZ dynamic exit - V9.5
« on: March 23, 2017, 07:57:33 AM »
Starting a new thread to get more visibility.   Thanks

I have been struggling to get this resolved and am hoping someone has been there and done that.

We are going from V9.0 to V9.5, using the ODSXUPDZ in V9.0 is working just fine with the ARS.RSADUPDT exit.

I compiled the ARSUUPDC using the supplied ARSUUPDJ JCL and deployed to the /bin/exits
I made minor changes to ARSUUPDC to display/debug some info and update a value to confirm it passes the updates out to the MVS exit RSA.ARSUUPDT.

ARSUUPDC - in OMVS

working storage
copy arsuupda.

call ARSZUXPL-MODFCNP using by reference ARSUUPDA
returning rc

My understanding is this call to ARSZUXPL-MODFCNP triggers the MVS exit RSA.ARSUUPDT


ODSXUPDZ - MVS

Linkage Section.

copy ARSUUPDA.

Procedure Division using
by reference ARSUUPDA.

The logging/debug of the MVS exit shows that the ARSUUPDA values are received and then updated successfully.

However the OMVS Exit ARSUUPDA logging/debug shows it doesn’t see the values modified by MVS exit.

In MVS – Display the results
Code
String ' ARSUUPDA-UPDATE = ' Pic-X8-2-98
' / X''' Pic-X200(1:8) ''''
delimited by size into SYSOUTZ-DATA.

Results
ARSUUPDA-UPDATE = 00000001 / X'00000001'

In OMVS
Display "UPDATE Value: " ARSUUPDA-UPDATE upon syspunch

Results
UPDATE Value: 000000000 UPDTEXIT

Is there some other step I need to turn on to ensure the values are read correctly in ARSUUPDC after ODSXUPDZ.

I will admit I am not an experienced COBOL programmer so if there is something you think might help, please suggest anything

99
z/OS Server / Re: Cobol ARSUUPDZ dynamic exit
« on: March 22, 2017, 12:40:52 PM »
I have been struggling to get this resolved and am hoping someone has been there and done that.

We are going from V9.0 to V9.5, using the ODSXUPDZ in V9.0 is working just fine with the ARS.RSADUPDT exit.

I compiled the ARSUUPDC using the supplied ARSUUPDJ JCL and deployed to the /bin/exits
I made minor changes to ARSUUPDC to display/debug some info and update a value to confirm it passes the updates out to the MVS exit RSA.ARSUUPDT.

ARSUUPDC - in OMVS

working storage
copy arsuupda.

call ARSZUXPL-MODFCNP using by reference ARSUUPDA
returning rc

My understanding is this call to ARSZUXPL-MODFCNP triggers the MVS exit RSA.ARSUUPDT


ODSXUPDZ - MVS

Linkage Section.

copy ARSUUPDA.

Procedure Division using
by reference ARSUUPDA.

The logging/debug of the MVS exit shows that the ARSUUPDA values are received and then updated successfully.

However the OMVS Exit ARSUUPDA logging/debug shows it doesn’t see the values modified by MVS exit.

In MVS – Display the results
Code
String ' ARSUUPDA-UPDATE = ' Pic-X8-2-98
' / X''' Pic-X200(1:8) ''''
delimited by size into SYSOUTZ-DATA.

Results
ARSUUPDA-UPDATE = 00000001 / X'00000001'

In OMVS
Display "UPDATE Value: " ARSUUPDA-UPDATE upon syspunch

Results
UPDATE Value: 000000000 UPDTEXIT

Is there some other step I need to turn on to ensure the values are read correctly in ARSUUPDC after ODSXUPDZ.

I will admit I am not an experienced COBOL programmer so if there is something you think might help, please suggest anything

100
MP Server / Re: Add field to AG via ARSXML
« on: March 14, 2017, 01:54:51 PM »
Sorry, haven't tried that but it should be available.   What I recommend is create a test AG with two or three of the values that you want in the dropbox using the admin GUI, then use ARSXML to unload/extract that AG.  I would then either mock up the extract file to match your requirements or use it as a guide to see how to define the fields.

101
MP Server / Re: Add field to AG via ARSXML
« on: March 14, 2017, 05:23:48 AM »
If I understand correctly you want to put the character '/' in a field name.   Replace the / with &# 47; (again remove the space).  That should work.

102
MP Server / Re: Add field to AG via ARSXML
« on: March 13, 2017, 12:21:24 PM »
You tried the escape charaters? 
Code: [Select]
& # 47 ;  - remove the spaces.

103
Report Indexing / Re: Performance of ACIF vs PDF Indexer
« on: January 27, 2017, 10:04:07 AM »
PPDs are supposed to be as fast as gets for PDF documents.   Can you share the all PDF Indexing message?

104
MP Server / Re: CMOD commands - How to capture return code
« on: January 09, 2017, 10:32:42 AM »
Windows Solution:   echo Exit Code is %errorlevel%

After issuing the ARSLOAD command use whatever process to capture the return code from variable %errorlevel%

Example :

ARSLOAD -H TEST -a NORPTFOUND
set ARSLOAD_RC=%errorlevel%
echo %ARSLOAD_RC%


Returns :
6

105
MP Server / Re: CMOD commands - How to capture return code
« on: January 09, 2017, 10:08:42 AM »
I know this is out of date but did you figure out a solution?   I want to also issue the ARSLOAD command from my JCL and then capture the return code to ensure the archive is successful.

Pages: 1 2 3 4 5 6 [7] 8 9 10