Messages

31

z/OS Server / ODF Customized e-mail Subject

« on: January 17, 2020, 07:39:11 AM »

Hello all,
We're in need to customize the Subject line for "specific" recipient only.  The arsodf.xml comments seems to suggest that you can do this by using the <Recipient> tag under the <EmailAttachmentNotify> section.  It's not clear wether the <Name> tag should specify the RECIPIENT or RECIPIENT LIST or does it matter.  I've tried everything including the actual e-mail address in the <Name> tag under <Recipient> to no avail.  The only thing that seems to work is the "default" Subject immediately following <EmailAttachmentNotify>.

Any ideas?

32

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 18, 2019, 06:48:12 AM »

Thanks all for the help and ideas.  I was able to get it to work with the following transform.xml.  The documentation and rjrussel's recommended transform had issues with incompatibility errors when I tried using it.  I also had to add the record format switch to Variable otherwise the document would not display properly.

<?xml version="1.0" encoding="utf-8"?>
<Transforms>
 <transform>
     <TransformName>line2pdf-default</TransformName>
     <TransformDescription>ARSXLINE Line2PDF transform</TransformDescription>
     <OutputMimeType>application/pdf</OutputMimeType>
     <OutputExtension>pdf</OutputExtension>
     <ODFileType>L</ODFileType>
    <CmdParms>
      <CCANSI>-a A</CCANSI>
      <LINEDELIMITER>-d</LINEDELIMITER>
      <INPUTFILE>-i</INPUTFILE>
      <OUTPUTFILE>-o</OUTPUTFILE>
    </CmdParms>
    <CmdLineExe>//opt//IBM//ondemand//V9.5//bin//arsxline</CmdLineExe>
    <OperationName>arsxline</OperationName>
    <Passthru>
        <cmdlineparm>-x P -a A -f V</cmdlineparm>
    </Passthru>
   </transform>
</Transforms>

33

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 17, 2019, 02:01:24 PM »

So I created the transform.xml for CMOD V9.5 on AIX.  I used the "line2pdf-default" transform name but am receiving the following:

CIWEB1807: The line data file could not be converted to a PDF file by using the Line2PDF configuration file.
The custom transform configuration file, transform.xml, does not include an entry for a Line2PDF transform.
Ask your administrator to update the custom transform configuration file for the repository.


I've confirmed the location of the transform.xml and included it in the Repository being used as documented in the manual.  Here's my transform.xml:

<?xml version="1.0" encoding="utf-8"?>
<Transforms>   
 <transform>
     <TransformName>line2pdf-default</TransformName>
     <TransformDescription>ARSXLINE Line2PDF transform</TransformDescription>
     <OutputMimeType>application/pdf</OutputMimeType>
     <OutputExtension>pdf</OutputExtension>
     <ODFileType>L</ODFileType>
     <CmdParms>
        <CCANSI>-a A</CCANSI>
        <CCMACHINE>-a M</CCMACHINE>
        <CCNONE>-a N</CCNONE>
        <CODEPAGE>-c</CODEPAGE>
        <LINEDELIMITER>-d</LINEDELIMITER>
        <RECORDFORMATFIXED>-f F</RECORDFORMATFIXED>
        <RECORDFORMATVARIABLE>-f V</RECORDFORMATVARIABLE>
        <RECORDFORMATSTREAM>-f S</RECORDFORMATSTREAM>
        <FONTNAME>-F</FONTNAME>
        <PAGEHEIGHTPIXELS>-h</PAGEHEIGHTPIXELS>
        <RECORDLENGTH>-l</RECORDLENGTH>
        <MARGIN>-m</MARGIN>
        <FONTSIZE>-n</FONTSIZE>
        <PRMODENONE>-p N</PRMODENONE>
        <PRMODESOSI1>-p 1</PRMODESOSI1>
        <PRMODESOSI2>-p 2</PRMODESOSI2>
        <PRMODESOSI3>-p 3</PRMODESOSI3>
        <LINEPERPAGE>-q</LINEPERPAGE>
        <LINEPERPRINTPAGE>-Q</LINEPERPRINTPAGE>
        <LINESPACINGFACTORDIV100>-s</LINESPACINGFACTORDIV100>
        <TRCNO>-t 0</TRCNO>
        <TRCYES>-t 1</TRCYES>
        <PAGEWIDTHPIXELS>-w</PAGEWIDTHPIXELS>
        <INPUTFILE>-i</INPUTFILE>   
        <OUTPUTFILE>-o</OUTPUTFILE>
    </CmdParms>
    <CmdLineExe>/opt/IBM/ondemand/V9.5/bin/arsxline</CmdLineExe>
    <OperationName>arsxline</OperationName>
    <Passthru>
        <cmdlineparm>-x P</cmdlineparm>
    </Passthru>
   </transform>

34

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 17, 2019, 11:13:24 AM »

Thanks!  This helps.  I give that a  shot and report back.

35

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 16, 2019, 11:52:53 AM »

Yes.  I did read the 'contanct your ibm rep.' which I don't know what that means.  This is on an AIX environment.  ICN and ODEWK both reside on AIX.  The Ondemand Server is on z/OS.  I looked in the /opt/IBM/ondemand/V9.5/www directories where ODWEK is installed but do not see any line2pdf.* files at all.

36

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 16, 2019, 08:15:45 AM »

Thanks but I think that's just a utility to convert line data to UTF-8.  I'm looking for the Line2PDF transform which ICN can use to convert line-data to PDF form (instead of using the line data viewer java applet)

37

Content Navigator / Line2PDF viewer/transform anyone?

« on: August 16, 2019, 06:40:00 AM »

Running ICN 3.0.6 on AIX with ODWEK 9.5 and OnDemand on z/OS DB2 V11.1.  I'd like to use the Line2PDF viewer documented in the ICN documentation but not sure where to find it.  I found indication that it is provided with CMOD 9.5 but it is nowhere to be found.  I also looked in CMOD 10.1 not to be found either.  Can anyone point me in the right direction?

38

z/OS Server / Re: CMOD 9.5 (maybe 10) and OSPROTECT?

« on: January 18, 2019, 11:13:33 AM »

Aha!  I just remembered this:

Had a report of a S0C4 in ARSSOCKD after rolling out maintenance that included OSPROTECT.

Turned out the maintenance included this:

http://www.odusergroup.org/forums/index.php?topic=1525.msg9989#msg9989

Ed

Thanks Ed!  The PTFs are for DB2 Query Monitor and the common component and it's impacting several DB2 applications at our shop.  We're putting in a new release of the products including the PTFs.

39

z/OS Server / CMOD 9.5 (maybe 10) and OSPROTECT?

« on: January 17, 2019, 11:52:34 AM »

We recently installed APAR OA54807 which enables z/OS to use the OSPROTECT parameter in IEASYSxx.  After installing this APAR we immediately ran into S0C4 in the ARSSOCK server.  I searched for CMOD maintenance and did not find anything.  Has anyone run into a similar issue with OSPROTECT and CMOD?

40

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 08, 2017, 02:52:59 PM »

Thanks to your help scottnys I've been able to get what I needed done by coding an Input Exit as suggested.  It's a bit convoluted but it works!

41

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 05, 2017, 08:44:16 AM »

Thank you for the suggestions and information.  It's been very helpful.  Tried going the ODF route with the fixed length records.  Works great except, already loaded reports with variable length do not display correctly.  Any thoughts?

42

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 11:38:11 AM »

I have tried using ODF to spit out the report and load it back into a new Application BUT, the report has an LRECL of 32K in JES.  When the report gets loaded into the new Application, the line output goes from 133 bytes to 32K and it's extremely slow to page through -- any thoughts about this?

On the full report browse, I got it to work in the "fat" client but, what about WEBi?  I don't see the option there.

43

z/OS Server / Re: How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 10:57:55 AM »

Thanks for the reply.  Yes we are breaking on the index field but we do not want to change the current folder view but rather create another folder with a different view such that the index field is not there but I can see ALL of the report (without BREAKS).

I looked at the "full report browse" option in the Folder definition but that does not seem to have any effect on the viewing -- it only shows the report for the indexed item and not ALL indexed items.

44

z/OS Server / How to setup a folder with different unique field for index-loaded data.

« on: May 04, 2017, 07:59:03 AM »

We have a need to view reports currently residing in CMOD/OAM in a different manner than being shown in current folders.  The data being loaded today has 2 fields; one is an index the other defaults to the current date/time value as the data gets loaded.   The folders have both fields defined which the user can use to search and make a selection.

We’d like to setup a new folder which would eliminate the index field and just show the “unique” date/time field for selection.  The problem we have is that the data is already stored using the index field so when a new folder is created with just the date/time field, duplicate entries are displayed.

Can I create a folder that shows the report by the unique date/time field without having to reload the data into a new Application/Application Group?

45

z/OS Server / Re: How to make fallback from upgrade?

« on: March 08, 2017, 09:00:24 AM »

I wanted to circle back and let everyone know how we "sort of" simplified the fallback to the previous (8.5) release from 9.5.  As you know, going to a new release "may" and "will" change the structure of tables, columns, tablespaces, etc.  The only clean way to return to the old release would be to return to the same database structure. Now that we have tested this process and it works well but, you will need DBA (and tools) help.  Note also that I'm only posting on the DB2 aspect of the fallback and not the entire fallback.

We start off by using IBM's DB2 Tools to "migrate" the current database (ARSDBASE) to a new database (XRSDBASE).  The tool extracts the DDL from the current database and unloads all tablespaces and tables as well.  It will then create a new database (XRSDBASE) using the DDL and LOAD all tables.  This essentially is creating a mirror copy of the ARSDBASE "prior" to migrating to the new release.

Once the copy of the database has been performed, we then perform the migration of OnDemand to the new release.

To fallback to the previous release/database you have 2 choices: 1: point OnDemand to the migrated database XRSDBASE or 2: drop and recreate the ARSDBASE using the reverse process of copying from XRSDBASE.

We chose option 1 by configuring OnDemand to use a new (XRSDBASE) database which in turn returned it to the 8.5 release.  Here are the high-level steps we followed:

1. Shutdown CMOD
2. Restore the OnDemand PDS's to the previous release
3. Mount the previous release zFS/HFS on its production mountpoint
4. Backout any PROCLIB changes made
5. Recompile and BIND any exits and/or in-house written programs
6. Reload any dynamic exits (SETPROG EXIT)
7. Reconfigure OnDemand to use new database
8. Restart CMOD and test

As I mentioned, we have performed this migration and fallback scenario and it has worked successfully for us. 

Then there's the issue of missing loads which you will have to work around.

Hope this helps.