|
View previous topic :: View next topic
|
| Author |
Message |
PhilDeVries
New User
.jpg)
Joined: 20 Mar 2010
Posts: 4
Location: Grand Rapids, MI USA
|
|
|
|
We are adding comment records to our Metacode printstream (i.e., adding x'03' in control character) that we need to use in subsequent applications for indexing purposes.
During our initial testing we were happily adding these comment records and writing our DD out to a file and verified that the comment recs were in the file correctly.
However, when we send the same output to the JES spool the comment records appear to be stripped out by something as they are not in the file viewed when viewed via SDSF =s.o in the output queue/spool.
How do I get the system to not strip the comment records out of the printstream before writing to the JES Spool?
Notes -
We are using Oracle product DocuMerge v3.2 to add these comment records to the printstream via the USER.TAG option. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
the record with 03 CCW command code /carriage control chars do not get written to the real printer
because the 03 CCW command code is a NOOP |
|
| Back to top |
|
|
PhilDeVries
New User
Joined: 20 Mar 2010
Posts: 4
Location: Grand Rapids, MI USA
|
|
|
|
| I would like to force the system to write the NOOP records out to the real printer, is there a way to accomplish this? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
so what You would like to have is a printing NOOP 
remember from a channel architecture point of view
the command codes ending with .3 and .b are immediate command codes
and no data transfer takes place anyway
the data transfer command codes are those ending with .1 and .9
( non immediate )
I just run a quick test and found that
| Code: |
//IBMUSERZ JOB CLASS=A,NOTIFY=&SYSUID,MSGCLASS=X
//IEB EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD *
/* 01 WRITE WITHOUT SPACING */
/* 03 SPACE 0 LINES IMMED ==> CONTROL NO-OPERATION */
/* 09 WRITE AND SPACE 1 LINE */
/* 0B SPACE 1 LINE IMMED */
/* 11 WRITE AND SPACE 2 LINES */
/* 13 SPACE 2 LINES IMMED */
/* 19 WRITE AND SPACE 3 LINES */
/* 1B SPACE 3 LINES IMMED */
/* 03 CONTROL NO-OPERATION */
/* 09 WRITE AND SPACE 1 LINE LAST LINE */
//SYSUT2 DD SYSOUT=*,RECFM=FBM,LRECL=80,BLKSIZE=80
|
and the output looks like
| Code: |
DATA SET UTILITY - GENERATE
PROCESSING ENDED AT EOD
/* 01 WRITE WITHOUT SPACING */
/* 09 WRITE AND SPACE 1 LINE */
/* 11 WRITE AND SPACE 2 LINES */
/* 19 WRITE AND SPACE 3 LINES */
/* 09 WRITE AND SPACE 1 LINE LAST LINE */
|
a SDSF SET HEX showed them
| Code: |
/* 09 WRITE AND SPACE 1 LINE */
0654FF4EDCEC4CDC4EDCCC4F4DCDC444456444444444444444444444444444444444444444444444
91C009069935015402713501039550000C1000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
04444444444444444444444444444444444444444444444444444444444444444444444444444444
B0000000000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
/* 11 WRITE AND SPACE 2 LINES */
1654FF4EDCEC4CDC4EDCCC4F4DCDCE44456444444444444444444444444444444444444444444444
11C011069935015402713502039552000C1000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
14444444444444444444444444444444444444444444444444444444444444444444444444444444
30000000000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
/* 19 WRITE AND SPACE 3 LINES */
1654FF4EDCEC4CDC4EDCCC4F4DCDCE44456444444444444444444444444444444444444444444444
91C019069935015402713503039552000C1000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
14444444444444444444444444444444444444444444444444444444444444444444444444444444
B0000000000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
04444444444444444444444444444444444444444444444444444444444444444444444444444444
30000000000000000000000000000000000000000000000000000000000000000000000000000000
------------------------------------------------------------------------------
/* 09 WRITE AND SPACE 1 LINE LAST LINE */
0654FF4EDCEC4CDC4EDCCC4F4DCDC4DCEE4DCDC45644444444444444444444444444444444444444
91C0090699350154027135010395503123039550C100000000000000000000000000000000000000 |
something has changed in jes2 some time ago..
looks like now jes2 stores data in the spool according to data/non data opcode
I remember that once upon a time the 03 opcode data was stored in the spool ( SCRPT/VS reminiscences ) with the output dvice class used for scripting |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
Enrico,
Your SDSF HEX screen print DOES show a x'03' record near the bottom! |
|
| Back to top |
|
|
PhilDeVries
New User
Joined: 20 Mar 2010
Posts: 4
Location: Grand Rapids, MI USA
|
|
|
|
Kind of...
I need two things to happen to this print file:
1) Print It
- Send it to Oce Prisma Production Server (Print Operator Console Application))
2) Prep for Reprint Capability
- Send to a Bowe Bell & Howell Recompose Server who parses the printfile into proprietary format (based on my NOOP Index records...that aren't working javascript:emoticon(' ')) for subsequent Reprint Capability.
I thought the NOOP's would be a cool method to allow me to inject indexing information within the print stream AND save on bandwidth, as the Prisma Server and the BBH Recompose Server are in the same room (i.e., I could send it from the Spool to Prisma, who would then have a script to send it to BBH Recompose).
I spoze I will just write the printstream out to a file and then:
1) iebgener it out to the Output Spool (with NOOP recs stripped by JES)
2) ftp it down to the BBH Recompose server (with NOOP recs intact)
Thanks for you time and input, I appreciate it! |
|
| Back to top |
|
|
PhilDeVries
New User
Joined: 20 Mar 2010
Posts: 4
Location: Grand Rapids, MI USA
|
|
|
|
Bill,
Yes, I can get the x'03' records to show up, but the data associated with them is not included. I was hoping to treat the NOOP recs as comment records and transfer indexing data in them to subsequent applications that injest our printstreams from the JES Output spool.
Here is what I see:
1) Write to File - NOOP's and Data included
2) Write to SYSOUT=* (SDSF =s.st) - NOOP's without Data
3) Write to SYSOUT OUTPUT= (SDSF =s.o) - NOOP's not written out at all. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| Your SDSF HEX screen print DOES show a x'03' record near the bottom! |
but no data in it, as I pointed out in the ccw opcode description before the pasted data!
looks like the only solution is route the sysout to a file and FTP the whole stuff |
|
| Back to top |
|
|
|
|
