OPALE - 10.0 - Utilisation - Tri et regroupement de spools - MAPSORTPAG/en

Différence entre versions

De MappingDoc
(Page créée avec « test 180 under MAP400/UCS2) +++++++++++++++++++++++++++++++ »)
 
(47 révisions intermédiaires par 3 utilisateurs non affichées)
Ligne 1 : Ligne 1 :
===CHGSPLFA with MAPSORTPAG===
+
<languages />
 +
===Changing a spooled file attribute using MAPSORTPAG===
 
Changing the FORMTYPE of a spooled file generated by MAPSORTSPL can be done in two different ways.
 
Changing the FORMTYPE of a spooled file generated by MAPSORTSPL can be done in two different ways.
  
It depends of how many spooled files are in the MAPSORTSPL output queue:
+
It depends on how many spooled files are in the MAPSORTSPL output queue:
  
 
1.
 
1.
Ligne 9 : Ligne 10 :
 
CHGSPLFA FILE(MYSPOOL) SPLNBR(*LAST) FORMTYPE(MYFORMTYPE)
 
CHGSPLFA FILE(MYSPOOL) SPLNBR(*LAST) FORMTYPE(MYFORMTYPE)
  
MYSPOOL being the name of the spooled file generated by command MAPSORTSPL
+
Where MYSPOOL is the name of the spooled file generated by the MAPSORTSPL command
  
  
 
2.
 
2.
 
If there are multiple spooled files in the MAPSORTSPL output queue, then you need to execute an action on all output spooled files, this means that you will need to:
 
If there are multiple spooled files in the MAPSORTSPL output queue, then you need to execute an action on all output spooled files, this means that you will need to:
:*Create MAPSORTSSPL output spooled files in one of the robot's input Outq
+
:*Create MAPSORTSPL output spooled files in one of the robot's input Outq
 
:*Create a new action to change the FORMTYPE and transfer the spooled files in the printing Outq:
 
:*Create a new action to change the FORMTYPE and transfer the spooled files in the printing Outq:
 
e.g. CHGTYPE with command CHGSPLFA FILE(&SPLF) JOB(&JOBNU/&USER/&JOB) SPLNBR(&SPLNUM)  
 
e.g. CHGTYPE with command CHGSPLFA FILE(&SPLF) JOB(&JOBNU/&USER/&JOB) SPLNBR(&SPLNUM)  
Ligne 20 : Ligne 21 :
 
:*Define the spooled file - action relation for these spooled files
 
:*Define the spooled file - action relation for these spooled files
  
===MAPSORTPAG_v7-et Report===
+
===Example: Creating a fold with 8 pages maximum===
  
Pour pouvoir séparer un pli de plus de 8 pages en autant de plis que bécessaire, (si une facture fait 10 pages, l'enveloppe sera fermée sur la 8 ème page et une nouvelle enveloppe sera insérée pour les 2 pages suivantes), utilisez le paramètre QUOTA. Positionnez sa valeur à 8.
+
If an invoice is 10 pages long, the envelope will be folded on page number 8 and a new envelope will be used for the next two pages. To seperate a fold with more than 8 pages in the number of folds you would like, use the QUOTA parameter. Enter 8 to define its value.
--> Pas besoin de passer le paramètre CONTROLE à 'V' et le SORTPAGE à 'O' dans ce cas.
+
--> There is no need to add 'V' (Volume) to the CONTROLE parameter, nor to add 'O' to SORTPAGE.
Cordialement,
 
  
 
+
To control the number of pages in the physical file, run an SQL query such as:
ctrl nb pages in pf:
 
req SQL
 
 
select count(*) from SYLTST2/FA_EDA901 where numlgn = '0'
 
select count(*) from SYLTST2/FA_EDA901 where numlgn = '0'
  
 +
SOLUTION more than 66 lines:
 +
CHGPRTF MAPOUT
  
SOLUTION more than 66 lignes:
+
MAPSORTPAG > spooled file Height recovery problem > 66 lines
CHGPRTF MAPOUT
 
 
 
 
 
 
 
28/10/2010
 
 
 
MAPSORTPAG > spooled file recovery problem > 66 lignes
 
 
 
_________________________________________________________________________________
 
  
 
   test 180 under MAP400/UCS2)  
 
   test 180 under MAP400/UCS2)  
Ligne 48 : Ligne 39 :
  
 
###################
 
###################
# spool en entrée #  >>>  R58SA127 OUTQ/LIB > SYLVAIN/MAP400
+
# input spooled file #  >>>  R58SA127 OUTQ/LIB > SYLVAIN/MAP400
 
###################
 
###################
  
  Taille de la page :                             
+
  Page dimensions:                             
   Hauteur . . . . . . . . . . . . . . :  72   
+
   Height . . . . . . . . . . . . . . :  72   
   Largeur . . . . . . . . . . . . . . :  134 
+
   Width . . . . . . . . . . . . . . :  134 
  
  
 
#############
 
#############
# commande: #
+
# command: #
 
#############
 
#############
  
  
===> MAPSORTPAG SPLF(R58SA127) SPLNUM(39) JOB(QPRTJOB) JOBNUM(391742) USER(SDAN
+
  MAPSORTPAG SPLF(R58SA127) SPLNUM(39) JOB(QPRTJOB) JOBNUM(391742)  
GEL) KEYLINE(4) KEYCOL(66) KEYLGN(14) SPLFNAME(R58SA127_S) OUTQ(SYLVAIN) OUTQLIB (MAP400)                                                                         
+
            USER(SDANGEL) KEYLINE(4) KEYCOL(66) KEYLGN(14)  
 
+
            SPLFNAME(R58SA127_S) OUTQ(SYLVAIN) OUTQLIB (MAP400)                                                                         
 
 
 
 
 
 
>>>>>>> indication >>>  CHGPRTF MAPOUT  pour hauteur
 
  
______________________________________________________________________________
+
>>>>>>> specification >>>  CHGPRTF MAPOUT  for the height
  
probleme mapsortpag avec mapreport suite passage v7
+
=== problem mapsortpag with mapreport after updating to v7 ===
  
commandes SQL pour préparer SORTSIZUTF*: (une bonne fois pour toute)
+
Use command SQL to prepare for SORTSIZUTF*:  
*(PF tampon pour création auto du PF de MAPSORTPAG)
+
*(PF buffer to create MAPSORTPAG PF)
  
<code>
 
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PAGES SET DATA TYPE CHAR(10)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PAGES SET DATA TYPE CHAR(10)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PRTDTA SET DATA TYPE CHAR(1134)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PRTDTA SET DATA TYPE CHAR(1134)  CCSID 1208
Ligne 89 : Ligne 75 :
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE8 SET DATA TYPE CHAR(120)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE8 SET DATA TYPE CHAR(120)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE9 SET DATA TYPE CHAR(120)  CCSID 1208
 
ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE9 SET DATA TYPE CHAR(120)  CCSID 1208
</code>
 
 
dans chaque commande MAPRUNRPT:
 
ajouter paramètre:  DB.MAPPING_DATASTREM=UCS2
 
 
  
  
---------------------
+
Everytime you use MAPRUNRPT:
 +
add this parameter: DB.MAPPING_DATASTREM=UCS2
  
La documentation :
+
=== Documentation ===
  
Dans strsql, les données ne sont plus visualisable, il faut donc les convertir à la volée :
+
The data in strsql can no longer be seen, you need to convert it on the fly:  
 
  select cast(prtdta as char(255) ccsid 1147) from alexis/sortsizutf     
 
  select cast(prtdta as char(255) ccsid 1147) from alexis/sortsizutf     
  
  
Dans MapReport :
+
In Connect:
Les données sont nativement lues en UTF-8.  
+
Data is read natively in UTF-8.  
Il n’y a donc aucune modification à apporter pour une lecture simple d’une table :
+
You do not need to change anything to read a table:
  
                Read(mytable,"Select \"PRTDTA FROM TEST.ANTO\" ") { }
+
Read(mytable,"Select \"PRTDTA FROM TEST.ANTO\" ") { }
 
                 Write(mytable,0) { }
 
                 Write(mytable,0) { }
 
                 NextRead() { }
 
                 NextRead() { }
  
  
La seule condition est de lancer la commande maprunrpt avec le paramètre DB.MAPPING_DATASTREAM=UCS2 (sinon les caractères multi octet ne seront pas pris en charge)
+
You only need to run the maprunrpt command with parameter DB.MAPPING_DATASTREAM=UCS2 (otherwise, multibyte characters will not be supported)
  
  
Attention :  
+
Caution:  
  
Lorsqu’on souhaite faire un lien entre une table classique en EBCDIC et une table en UTF-8, la clause where TABLE_EBCDIC.CHAMP1 = TABLE_UTF8.CHAMP1 ne marche plus.  
+
When you wish to link an EBCDIC table and one in UTF-8, the clause where TABLE_EBCDIC.CHAMP1 = TABLE_UTF8.CHAMP1 does not work anymore.  
C’est logique car les datas ne sont pas dans le mêmes encodage. Pour cela, il faut appliquer un cast sur les champs :
+
It doesn't because data isn't contained in the same encoding. Apply a cast on field:
 
Read(TABLE_UTF8,"Select … From … Where cast(BIB.TABLE_UTF8.CRITERE0 as char(8) ccsid 37) =  $TABLE_EBCDIC.CRITERE ") { }
 
Read(TABLE_UTF8,"Select … From … Where cast(BIB.TABLE_UTF8.CRITERE0 as char(8) ccsid 37) =  $TABLE_EBCDIC.CRITERE ") { }
  
Ici, on a casté le champ CRITERE0 de la table UTF8 en ccsid 37 (ebcdic) pour que la base puisse faire la comparaison.
+
In this example we casted field CRITERE0 from the UTF8 table in ccsid 37 (ebcdic) so that the database can work out the difference between the two.

Version actuelle datée du 9 octobre 2019 à 09:10

Autres langues :
English • ‎français

Changing a spooled file attribute using MAPSORTPAG

Changing the FORMTYPE of a spooled file generated by MAPSORTSPL can be done in two different ways.

It depends on how many spooled files are in the MAPSORTSPL output queue:

1. If there's only one spooled file in the MAPSORTSPL output queue, then run command CHGSPLFA combine it with another command such as CHGSPLFA FILE(MYSPOOL) SPLNBR(*LAST) FORMTYPE(MYFORMTYPE)

Where MYSPOOL is the name of the spooled file generated by the MAPSORTSPL command


2. If there are multiple spooled files in the MAPSORTSPL output queue, then you need to execute an action on all output spooled files, this means that you will need to:

  • Create MAPSORTSPL output spooled files in one of the robot's input Outq
  • Create a new action to change the FORMTYPE and transfer the spooled files in the printing Outq:

e.g. CHGTYPE with command CHGSPLFA FILE(&SPLF) JOB(&JOBNU/&USER/&JOB) SPLNBR(&SPLNUM) FORMTYPE(MYFORMTYPE) OUTQ(MYLIB/MYPRINTER)

  • Define the spooled file - action relation for these spooled files

Example: Creating a fold with 8 pages maximum

If an invoice is 10 pages long, the envelope will be folded on page number 8 and a new envelope will be used for the next two pages. To seperate a fold with more than 8 pages in the number of folds you would like, use the QUOTA parameter. Enter 8 to define its value. --> There is no need to add 'V' (Volume) to the CONTROLE parameter, nor to add 'O' to SORTPAGE.

To control the number of pages in the physical file, run an SQL query such as: select count(*) from SYLTST2/FA_EDA901 where numlgn = '0'

SOLUTION more than 66 lines: CHGPRTF MAPOUT

MAPSORTPAG > spooled file Height recovery problem > 66 lines

  test 180 under MAP400/UCS2) 
 +++++++++++++++++++++++++++++++


  1. input spooled file # >>> R58SA127 OUTQ/LIB > SYLVAIN/MAP400
Page dimensions:                             
  Height  . . . . . . . . . . . . . . :   72   
  Width  . . . . . . . . . . . . . . :   134  	


  1. command: #


 MAPSORTPAG SPLF(R58SA127) SPLNUM(39) JOB(QPRTJOB) JOBNUM(391742) 
           USER(SDANGEL) KEYLINE(4) KEYCOL(66) KEYLGN(14) 
           SPLFNAME(R58SA127_S) OUTQ(SYLVAIN) OUTQLIB (MAP400)                                                                        

>>>>>>> specification >>> CHGPRTF MAPOUT for the height

problem mapsortpag with mapreport after updating to v7

Use command SQL to prepare for SORTSIZUTF*:

  • (PF buffer to create MAPSORTPAG PF)

ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PAGES SET DATA TYPE CHAR(10) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN PRTDTA SET DATA TYPE CHAR(1134) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE0 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE1 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE2 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE3 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE4 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE5 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE6 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE7 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE8 SET DATA TYPE CHAR(120) CCSID 1208 ALTER TABLE MAP400/SORTSIZUTF ALTER COLUMN CRITERE9 SET DATA TYPE CHAR(120) CCSID 1208


Everytime you use MAPRUNRPT: add this parameter: DB.MAPPING_DATASTREM=UCS2

Documentation

The data in strsql can no longer be seen, you need to convert it on the fly:

select cast(prtdta as char(255) ccsid 1147) from alexis/sortsizutf    


In Connect: Data is read natively in UTF-8. You do not need to change anything to read a table:

Read(mytable,"Select \"PRTDTA FROM TEST.ANTO\" ") { }

               Write(mytable,0) { }
               NextRead() { }


You only need to run the maprunrpt command with parameter DB.MAPPING_DATASTREAM=UCS2 (otherwise, multibyte characters will not be supported)


Caution:

When you wish to link an EBCDIC table and one in UTF-8, the clause where TABLE_EBCDIC.CHAMP1 = TABLE_UTF8.CHAMP1 does not work anymore. It doesn't because data isn't contained in the same encoding. Apply a cast on field: Read(TABLE_UTF8,"Select … From … Where cast(BIB.TABLE_UTF8.CRITERE0 as char(8) ccsid 37) = $TABLE_EBCDIC.CRITERE ") { }

In this example we casted field CRITERE0 from the UTF8 table in ccsid 37 (ebcdic) so that the database can work out the difference between the two.