Release Notes. StreamWeaver Contents

Transcription

1 Release Notes StreamWeaver Technical Support This document contains information about the StreamWeaver release. Complete documentation and global contact numbers can be found on the technical support website at :30 AM to 8:00 PM EST Monday through Friday Knowledge Base Contents What s New Fixed Issues Blog ebs.pbbiblogs.com 1

2 What s New What s New This release contains new and changed Tags and Messages: Tags <ATTACH> <DATAMATRIX> <IMMATTACH> <PDF417> <ATTACH> This new tag in the <FIELD> tag group controls the retention of field values when performing PAGE level processing in the rule file. When a field value is not found on a page, StreamWeaver sets the value to the value on the previous page. To prevent field value retention, add an <ATTACH> tag to the <FIELD> tag group and set the value to No. For more information, see New Tag: <ATTACH> (CR ) and the StreamWeaver Language Reference. <DATAMATRIX> A new parameter was added to this tag to control EBCDIC-to-ASCII translation. The expanded syntax is: <DATAMATRIX> squareyn [errorcorrection encodemode translateyn] If set to Yes, then the contents of the DataMatrix barcode will be translated from EBCDIC to ASCII. If set to No, the contents will remain as is. This fix applies only to StreamWeaver running on the Z/OS platform. For more information, see Invalid PDF417 Barcodes (CR ) and the StreamWeaver Language Reference. <IMMATTACH> This new tag in the <ENVIRONMENT> tag group determines whether or not to keep track of which IMM is applicable to a particular AFP page on input, and ensure that it is applied to that page on output, even if reordered. For more information, see the StreamWeaver Language Reference. 2

3 What s New <PDF417> A new parameter was added to this tag to control EBCDIC-to-ASCII translation. The expanded syntax is: <PDF417> aspect [errorcorrection translateyn] If set to Yes, then the contents of the PDF417 barcode will be translated from EBCDIC to ASCII. If set to No, the contents will remain as is. For more information, see Invalid PDF417 Barcodes (CR ) and the StreamWeaver Language Reference. Messages PDR1505W PDR1506S PDR1507S PDR3211S PDR3232S PDR1505W <COLOR> ignored for MaxiCode. What happened: The <COLOR> tag is specified in a MaxiCode type (<ADDTYPE> X). MaxiCode barcodes are black-and-white only. The <COLOR> tag is ignored. What to do: Remove <COLOR> tag. PDR1506S Invalid <PDF417> parameter %%var1%%. Value must be YES or NO. What happened: You specified a value other than Yes or No for the <PDF417> tag. The invalid value is given. What to do: Specify the parameter for <PDF417> as either Yes (translate the contents of the PDF417 barcode from EBCDIC to ASCII) or No. PDR1507S Invalid <DATAMATRIX> parameter %%var1%%. Value must be YES or NO. 3

4 What s New What happened: You specified a value other than Yes or No for the <DATAMATRIX> tag. The invalid value is given. What to do: Specify the parameter for <DATAMATRIX> as either Yes (translate the contents of the DATAMATRIX barcode from EBCDIC to ASCII) or No. PDR3211S Invalid <IMMATTACH> parameter %%var1%%. Value must be YES or NO. What happened: You specified a value other than Yes or No for the <IMMATTACH> tag. The invalid value is given. What to do: Specify the parameter for <IMMATTACH> as either Yes (keep track of what IMM is applicable to a particular AFP page on input, and ensure that it is applied to that page on output, even if reordered) or No. PDR3232S Invalid <ATTACH> parameter. Value must be YES or NO. What happened: You specified an invalid value for <ATTACH>. What to do: Specify YES or NO. 4

5 Fixed Issues Fixed Issues This release contains fixed issues for the following: Missing Framing Characters (CR ) New Tag: <ATTACH> (CR ) Misplaced Barcode Symbols (CR ) Processing Error with PostScript (CR ) %%SEQUENCE_NO System Variable Error (CR ) Invalid PDF417 Barcodes (CR ) <COLOR> Tag Ignored (CR ) <RESOURCESCAN> Tag Processing Error (CR ) <POSITION> tag with variables not working at PAGE level (CR ) Message PDR2002S: Unable to acquire and copy bytes of memory for Page structure. (CR ) Missing Framing Characters (CR ) Reported Problem: StreamWeaver does not generate the PDR1451W message when POSTNET and PLANET barcodes with missing framing characters are encountered. Change in behavior: The message now correctly displays when missing framing characters are encountered. See the StreamWeaver Messages Reference for more information about this message. This fix applies only to AFP and Metacode print streams. NOTE: POSTNET is scheduled to be obsolete in May New Tag: <ATTACH> (CR ) Reported Problem: StreamWeaver retains previous field values if the value is NULL on a page. The problem occurs when using the field value in PAGE level processing and sorting the data. Change in behavior: To fix this problem, a new <ATTACH> tag is introduced to prevent field value retention when performing PAGE level processing. To prevent field value retention, add an <ATTACH> tag to the <FIELD> tag group and set the value to No. For more information about this tag, see the StreamWeaver Language Reference. 5

6 Fixed Issues A new PDR3232S message has been added in support of this tag. Additional Information: When a field value is not found on a page, StreamWeaver sets the field value to the value on the previous page. In order to add a flexible method for controlling this behavior, a new <ATTACH> tag has been added. To prevent field retention, add an <ATTACH> tag to the <FIELD> tag group and set the value to No. The syntax is: <ATTACH> attachyn The possible values are: YES: If the field is not found on the page, it retains the value from the previous page. NO: If the field is not found on a page, the field value is set to Null. The default is Yes. NOTE: Fields that have the <ATTACH> tag set to No will have Null values if used in a <SIDEPART> or <ADDPART> tag. Misplaced Barcode Symbols (CR ) Reported Problem: PCL 2OF5 barcode symbol of ORIENT 2, 3, and 4 are all misplaced, but the HRI is correctly placed. The problem is that text and drawn barcode PCL command respond different to the Print Direction Command. This defect is not customer-reported, but is a long-standing defect on PCL and Postscript barcodes. Change in Behavior: All barcodes are now drawn correctly as documented. NOTE: If you have written control files that expect the barcode to be placed in the correct position, this version of StreamWeaver may require that you remove these workarounds. 6

7 Fixed Issues Processing Error with PostScript (CR ) Reported Problem: StreamWeaver is unable to process PostScript files with very long records. Change in Behavior: PostScript files with very long records now process successfully. %%SEQUENCE_NO System Variable Error (CR ) Reported Problem: %%SEQUENCE_NO and %%TOT_SEQUENCE_NO have a value 1 greater in the DOCUMENT and PRESORTED sections of the rule file. There will no longer be a discrepancy in these system variables with their values in the PAGE section. Change in Behavior: %%SEQUENCE_NO is now synchronized with PAGE section processing. Additional Information: This change may introduce other issues for rule files created in previous StreamWeaver versions. A discrepancy in %%SEQUENCE_NO between the PAGE section and the DOCUMENT section can still occur if the <PAGERANGE> tag is used. The <PAGERANGE> tag is obsolete so if you are still using this tag, consider removing it from your control files. If you are using %%SEQUENCE_NO or %%TOT_SEQUENCE_NO in the DOCUMENT and PRESORTED sections of the rule file with a previous version of StreamWeaver, you may have different output with version %%FILEMAX_BEGIN currently stays at 1 for each document in the reject file when performing pre-sort. It will be reset to 0 on the second document. Every call to an <OUTPUT> command will increment the sequence number by 1 during an execution of the DOCUMENT section. For example, if the sequence number is examined before a call to the <OUTPUT> command and then examined again immediately after the call, it will have a value 1 greater than the previous value. Previously, the value would remain the same until the next execution of the DOCUMENT section. When a file break occurs, the sequence number will be set to 1 in the DOCUMENT section. Previously, the sequence number equaled the incremented value from the previous file. Invalid PDF417 Barcodes (CR ) Problem Reported: PDF417 produces invalid barcodes when data to be encoded contains binary zeros X'00'. Change in Behavior: StreamWeaver now produces scannable PDF417 barcodes. 7

8 Fixed Issues <COLOR> Tag Ignored (CR ) Problem Reported: The <COLOR> tag on MaxiCode drawing is not supported on all platforms. Change in Behavior: The MaxiCode symbol is black. A <COLOR> tag in the same <ADD> tag group is now ignored. Error message PDR1505W now displays when a <COLOR> tag is encountered in the same <ADD> tag group. <RESOURCESCAN> Tag Processing Error (CR ) Problem Reported: <RESOURCESCAN> processing is not finding all resources. Change in Behavior: <RESOURCESCAN> tag processing now finds all specified resources for all PCL documents. <POSITION> tag with variables not working at PAGE level (CR ) Problem Reported: <POSITION> tag with variables is not working at the PAGE level. If variables were changed in the PAGE section, the new values were not used. Change in Behavior: <POSITION> variables now work as designed. Message PDR2002S: Unable to acquire and copy bytes of memory for Page structure. (CR ) Reported Problem: The input AFPDS file contained an in-line resource group, in addition to embedded resources found within the document structure. StreamWeaver encountered this error on the Z/OS platform when processing the file. Change in Behavior: StreamWeaver now accurately creates all resources files and lists them in the resource log file. NOTE: StreamWeaver issues message PDR3206S if any of the embedded resource names do not comply with Z/OS file naming standards. Z/OS files cannot contain special characters such as a - ). 8

9 2010 Pitney Bowes Software, Inc. CASS, CASS Certified, DPV, elot, FASTforward, NCOA Link, LACS Link, Postal Service, Post Office, POSTNET, RDI, United States Post Office, USPS, United States Postal Service, ZIP Code, and ZIP + 4 are registered trademarks of United States Postal Service (USPS ). This list is not exhaustive of the trademarks belonging to the Postal Service. Pitney Bowes Software is a non-exclusive licensee of USPS for NCOA Link processing. Prices for Pitney Bowes Software products, options and services are not established, controlled or approved by USPS or United States Government. When utilizing RDI data to determine parcel-shipping costs, the business decision on which parcel delivery company to use is not made by the USPS or United States Government. Pitney Bowes Software, Inc. holds a nonexclusive license to publish and sell ZIP + 4 databases on optical and magnetic media. Pitney Bowes Business Insight 4200 Parliament Pl Ste 600 Lanham, MD Main: +1 (301) Sales: +1 (888) Support: +1 (800)