Messages

61

MP Server / Re: Issue with CMOD admin client, application and pdf index

« on: November 07, 2019, 09:09:56 AM »

The 64-bit administrator client does not have support for PDF sample data. If you use the 32-bit administrator client you should still be able to markup PDF data in the graphical indexer.

Likewise, the 64-bit Windows client does not have support for seamless viewing of PDF data, but the 32-bit Windows client does.

62

OD/WEK & JAVA API / Re: Searching mapped folder fields with multiple values

« on: November 04, 2019, 11:46:13 AM »

You might try two folder fields mapped to the same application group field, and then use a Logical Or search in the client. That would provide the capability to specify two values. I suppose it would work for more than two, but I have only tested with two.

63

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 16, 2019, 12:05:45 PM »

Ricoh sells the LINE2PDF transform
https://www.ricoh-usa.com/en/products/pd/software/commercial-industrial-printing-software/datastream-transforms/ricoh-web-enablement-solutions-suite/_/R-5876-W04-0001

64

Content Navigator / Re: Line2PDF viewer/transform anyone?

« on: August 16, 2019, 09:36:22 AM »

arsxline converts line to UTF-8 or PDF

        -a <cc_type> carriage control (default A - ANSI, M - Machine, N - None)         
        -c <cp> input data code page (default: 500)                                     
        -d <rec_delim> record delimiter (default: 0A)                                   
        -f <rec_fmt> record format (default F - Fixed, V - Variable, S - Stream)       
        -F <font_name> font name (default: Courier)                                     
        -g <pdf_image_file> pdf image file (.png or .jpg)                               
        -G <pdf_image_position> pdf image file position (default: 0,0 left,top)         
        -h <page_height> page height (default: 792)                                     
        -i <inp_file> input file                                                       
        -k <overstrike_mode> overstrike mode (default M - Merge, S - Separate, F - Full)
        -K <pdf_image_mode> pdf image mode (default A - All, F - First, L - Last)       
        -l <rec_len> fixed record length (default: 133)                                 
        -m <margin> margin (default: 36,36,36,36 top,bottom,left,right)                 
         -n <font_size> font size (default: 12)                                           
         -o <out_file> output file                                                       
         -O <orientation> (P - Portrait, L - Landscape)                                   
         -p <prmode> presentation mode (default N - None, 1 - SOSI1, 2 - SOSI2, 3 - SOSI3)
         -P <parm_file> parameter file                                                   
         -q <lines_per_page> lines per page (default: 0)                                 
         -Q <lines_per_print_page> - lines per print page (default: 0)                   
         -s <line_spacing_factor> line spacing factor (default: 1.6)                     
         -t <trc> trc (default 0 - No, 1 - Yes)                                           
         -w <page_width> page width (default: 612)                                       
         -x <transform_type> transform type (default U - UTF8, P - PDF)                   
         -1 <trace_file> Trace file                                                       
         -2 <trace_level> Trace level                                                     

65

Content Navigator / Re: Line2PDF viewer/transform anyone?

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

I believe you are looking for the arsxline command.

66

iSeries / Re: Can /QNTC file System be used in Generic Indexer IND file GROUP_FILENAME parm?

« on: August 02, 2019, 01:04:02 PM »

I suggest using QFileSvr400. This will make the directory appear local and without the need to preface the path with any new directory name.  I use this in testing all the time. For example:

On system B
ADDLNK OBJ('/QFILESVR.400/SystemA/sharename') NEWLNK('/sharename')

MD DIR('/QFILESVR.400/SystemA') DTAAUT(*RWX) OBJAUT(*ALL)

Each time you IPL you have to run the MD command on System A to 'mount' the directory on System B

In my experience, both systems have to use the same password length (don't mix 10 char max and 128 char max systems.) And I believe the password of the user doing the mount must be same on both systems.

67

z/OS Server / Re: LPD/LPR on CMOD

« on: March 28, 2019, 11:43:10 AM »

We have multiple companies that load spooled files from IBM i to z/OS or MP.  They run the load process on the IBM i system and the indexes and data are loaded on the z/OS or MP system.  Documentation can be found in support item 7014901 at ibm.com.  The document was last updated at v9.5 but the same techniques apply to v10.1. 

68

MP Server / Re: Loading AFP document using Generic Indexer

« on: March 01, 2019, 12:18:54 PM »

The generic indexer will not convert line data to AFP.  For that, you need to use ACIF.

69

MP Server / Re: Large Migration + Codepage

« on: October 30, 2018, 06:30:59 AM »

For IBM i customers using UTF-8, we provide this advice, which I think applies to all platforms.

When storing indexes in a UTF-8 instance, it is important to note that some characters will use more than one byte when stored in a UTF-8 field.  Latin lowercase and uppercase characters [a-z] [A-Z] and Arabic numerals [0-9] use only one byte.  Accented characters might use two bytes.  DBCS characters might use two or three bytes.

When using the graphical indexer of the OnDemand Administrator client with a UTF-8 instance, the Indexer Properties dialog will be presented before your sample data is displayed.  You must set the Code Page to the value that matches the data being indexed.

When indexes are stored, they are converted from the Code Page specified on the Indexer Properties dialog to UTF-8 (CCSID 1208).  String conversion between code pages might result in an increase in the length of the string when data is loaded on the server.  For example, the OnDemand Administrator client might require two bytes to display a double-byte character, yet the server might require three bytes to store the character in the database.

When storing data for languages such as Greek, Russian, and Arabic, it is recommended that you create application group string fields that are double the length you would use if the instance did not support UTF-8.  For other languages, if your index values contain accented characters, you will need to make the fields longer.

When selecting a string, the graphical indexer will set the Field Length to the length selected in the sample data.

On the Database Field Attributes tab, the graphical indexer increases the string length to a size that is sufficient to hold the data that you have selected.  If you expect that other possible values for the field might require more space than Content Manager OnDemand calculated, you can override the length by typing a different number in the space provided.

70

Report Indexing / Re: ACIF Indexer and Posting Date

« on: October 17, 2017, 02:18:51 PM »

I believe the first page is dropped because ACIF must find all the group triggers before it starts collecting fields.

From the indexing reference manual: 'All fixed group triggers must match before ACIF can generate index information.'

71

iSeries / Re: Arsdoc Print Date range not working

« on: October 17, 2017, 02:14:49 PM »

I have not been able to recreate your problem on our 9.5.0.7 and 9.5.0.9 test systems.  I tested with AGs using old style dates, new style dates, and a combination of both.

arsdoc query -v -h ondenu2  -f CHECKSP -i "WHERE ACCTNO = '140060161' AND ODDAT_ENDDATE BETWEEN '2014-12-01' AND '2014-12-31'"
2017-10-17 17:00:44.207600: ARS6108I Starting arsdoc.  Version:  9.5.0.7
2017-10-17 17:00:44.211632: ARS6165I QRDARS/ARSDOC query -v -h ondenu2 -f CHECKSP -i WHERE ACCTNO = '140060161' AND ODDAT_ENDDATE
 BETWEEN '2014-12-01' AND '2014-12-31'
2017-10-17 17:00:44.239080: ARS6062I Searching for folder 'CHECKSP' ...
2017-10-17 17:00:44.589280: ARS6084I Search successful
2017-10-17 17:00:44.589576: ARS6063I Searching for documents in 'CHECKSP' ...
2017-10-17 17:00:44.589808: ARS6117I Querying database with SQL string 'WHERE ACCTNO = '140060161' AND ODDAT_ENDDATE BETWEEN '201
4-12-01' AND '2014-12-31''
2017-10-17 17:00:44.970520: ARS6084I Search successful                   
MYRTLE BEACH BLANKET     ,140060161,651-0086375,12/19/14,513324.960000,01
MYRTLE BEACH BLANKET     ,140060161,651-0086375,12/19/14,513324.960000,01
MYRTLE BEACH BLANKET     ,140060161,651-0086375,12/19/14,513324.960000,01
2017-10-17 17:00:44.973776: ARS6026I arsdoc completed.

If I use other date formats or separators I receive the message: ARS6007E The server failed during a search operation.
The system log contains message 13, DB Error: Syntax of date, time, or timestamp value not valid. -- SQLSTATE=22007, SQLCODE=-180, File=arsdoc.c, Line=2997

If you have the AG set to log Query messages, you can check the actual query that is run.  In my case, the after query message 226s (one per AG), contain this"

Application Group Query: Name(CHECKSP005) Agid(9838) Time(0.013) Hits(1) Count() SegStart() SegStop() Tables(1) Sql(WHERE ACCTNO = '140060161' AND ODDAT_ENDDATE BETWEEN '2014-12-01' AND '2014-12-31') SqlR() FullTextSearch() FullTextScore() ServerTextSearch() AnnColor() AnnText() OrderBy()
and
Application Group Query: Name(CHECKSP004) Agid(9835) Time(0.032) Hits(2) Count() SegStart() SegStop() Tables(2) Sql(WHERE ACCTNO = '140060161' AND ODDAT_ENDDATE BETWEEN '2014-12-01' AND '2014-12-31') SqlR() FullTextSearch() FullTextScore() ServerTextSearch() AnnColor() AnnText() OrderBy()

The messages show the query used, the number of tables searched, and the number of hits returned.

72

iSeries / Re: Arsdoc Print Date range not working

« on: October 17, 2017, 07:33:05 AM »

What error do you receive then using YYYY-MM-DD?  Per this support item, the YYYY-MM-DD format is required:
http://www.ibm.com/support/docview.wss?uid=swg27036188

Also, are you planning to upgrade to v7.2 or v7.3 soon?  We added the commands PRTDOCOND, QRYDOCOND, and RTVDOCOND to provide an easy to use front end to arsdoc print, arsdoc query, and arsdoc get.  The commands are available at v7.2 and higher at sever version 10.1.

73

iSeries / Re: How to copy SCS Spool files to PC Files ?

« on: September 26, 2017, 08:26:07 AM »

The PRTDOCOND, QRYDOCOND, and RTVDOCOND commands are now available at v7.2.

74

iSeries / Re: Arsdoc Print Date range not working

« on: September 26, 2017, 08:08:58 AM »

Hello Brian,
The -S parameter is used to limit which application group index tables are searched.  The -S means 'segment date'.  The -S will only limit which tables are searched, not which records are returned.  To set a date range for which records are returned, you must use the -i parameter to specify an SQL WHERE clause.

For example:

arsdoc print -v -h ondenu -i "WHERE ODDAT_ENDDATE BETWEEN '2016-01-01' AND '2016-12-31'" -f CHECKSTMTSV -P PRT01

ENDDATE is the AG field name.  ODDAT_ is added at the beginning so that you don't need to be concerned if the AG is using old or new style date.

75

iSeries / Re: Migrating Archived documents from TSM back to either System ASP or iASP.

« on: December 19, 2016, 03:12:49 PM »

The TSM APIs were out of support on IBM i effective April 30, 2015.  A support item discussing the alternatives is available in support item "Alternatives for accessing Content Manager OnDemand for i data on Tivoli Storage Manager (TSM) storage nodes" at http://www.ibm.com/support/docview.wss?uid=swg21976801

If you are using TSM as the storage manager you have two choices:
1) Install an ODMP object server between your IBM i server and your TSM server
2) Use arsdoc get to retrieve all data stored in TSM and store it in new application groups that use ASM as the storage manager