{"id":7116,"date":"2018-11-27T18:01:20","date_gmt":"2018-11-27T18:01:20","guid":{"rendered":"https:\/\/alt2.minisoft.com\/support\/?p=7116"},"modified":"2022-05-13T11:35:24","modified_gmt":"2022-05-13T18:35:24","slug":"predefined-queue-monitor-variables","status":"publish","type":"post","link":"https:\/\/www.minisoft.com\/support\/predefined-queue-monitor-variables\/","title":{"rendered":"Predefined Queue Monitor Variables"},"content":{"rendered":"

For more on the iSeries, please consult the following resource: iSeries (AS\/400) Roadmap<\/a><\/p>\n

For more information on predefined queue monitor variables, view the following resource: Print Object Attributes<\/a><\/p>\n

Queue Monitor variables are defined in the Director Toolkit. They can be accessed in a project by defining a Queue Monitor variable and giving it the same name as the variable defined in the Director Toolkit.<\/p>\n

Setting AS400 Spool File Attributes<\/strong><\/h2>\n

You can get the JOBUSER, USERDATA, and other fields from the incoming spool file by creating a \u201cQueue Monitor Variable\u201d with one of the pre-defined values. (From the “Input Variables” table below)<\/p>\n

\"\"<\/a><\/p>\n

You can assign a string to one of attributes of the spool file(s) created by the project by creating Global Variables using the appropriate string. (From the “Output Variables” table below)<\/p>\n

\"\"<\/a><\/p>\n

Global variables are set to specific values using an action in a procedure.<\/p>\n

\"\"<\/a><\/p>\n

Setting up an eDIRECT process for output<\/h3>\n

The output type must be eDIRECT Output and not printer output in the Local Toolkit.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

Predefined Queue Monitor Variables<\/strong><\/h2>\n

Always:<\/strong>
\n“datafilename”
\n“datafileext”
\n“project”<\/p>\n

LocalQueueMonitor:<\/strong>
\n“directory”<\/p>\n

Output Only:<\/strong>
\n“ProjectStatus”
\n“QMComponentFiles”<\/p>\n

AS400 Only:<\/strong>
\nqueue
\niSeries_COPIES
\niSeries_USERDATA
\niSeries_USERDEFDATA
\niSeries_SAVE
\niSeries_JOBUSER
\niSeries_JOBNAME
\niSeries_SPFNAME
\niSeries_SPLFSTATUS
\niSeries_FILENUMBER
\niSeries_JOBNUMBER
\niSeries_FORMTYPE
\niSeries_AUX_POOL<\/p>\n

Notes:<\/em><\/strong><\/p>\n

\u2022 When ProjectStatus is set to “abort” an exception is thrown. If an AlertQueue<\/a> is set up to catch these errors, note that it will be activated with a Priority of 0, so unless your alert queue is handling level 0 messages it should not affect it.<\/p>\n

\u2022 A list of files can be sent back to the Queue Monitor through a global variable named “QMComponentFiles”. Those files listed will have the same disposition as the main data file. (A comma delimited string of file names.)<\/p>\n

Example<\/em>
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_SPFNAME = COLLATE
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_USERDATA = PK10RERP
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_JOBNAME = SDBLACKBUB
\n0000000088 (12\/1\/16 1:19:02 PM) datafileext =
\n0000000088 (12\/1\/16 1:19:02 PM) queue = \/QSYS.LIB\/QUSRSYS.LIB\/MINISOFT.OUTQ
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_SAVE = *YES
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_JOBUSER = SDBLACKBUR
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_COPIES = 1
\n0000000088 (12\/1\/16 1:19:02 PM) datafilename = COLLATE
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_USERDEFDATA = *NONE
\n0000000088 (12\/1\/16 1:19:02 PM) iSeries_SPLFSTATUS = *READY<\/p>\n

Input Variables:<\/strong>
\n( “iSeries_COPIES”);
\n( “iSeries_USERDATA”);
\n( “iSeries_USERDEFDATA”);
\n( “iSeries_SAVE”);
\n( “iSeries_JOBUSER”);
\n( “iSeries_JOBNAME”);
\n( “iSeries_SPFNAME”);
\n( “iSeries_SPLFSTATUS”);
\n( “iSeries_FILENUMBER”);
\n( “iSeries_JOBNUMBER”);
\n( “iSeries_FORMTYPE”);
\n( “iSeries_AUX_POOL”);<\/p>\n

Output Variables:<\/strong>
\n(“ATTR_USERDATA”);
\n(“ATTR_USRDEFDATA”);
\n(“ATTR_SAVE”);
\n(“ATTR_HOLD”);
\n(“ATTR_FORMTYPE”);
\n(“ATTR_SCHEDULE”);<\/p>\n","protected":false},"excerpt":{"rendered":"

For more on the iSeries, please consult the following resource: iSeries (AS\/400) Roadmap For more information on predefined queue monitor variables, view the following resource: Print Object Attributes Queue Monitor variables are defined in the Director Toolkit. They can be accessed in a project by defining a Queue Monitor variable and giving it the same name […]<\/p>\n","protected":false},"author":75,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[186],"tags":[81,168,779],"_links":{"self":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7116"}],"collection":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/users\/75"}],"replies":[{"embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=7116"}],"version-history":[{"count":9,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7116\/revisions"}],"predecessor-version":[{"id":10334,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/posts\/7116\/revisions\/10334"}],"wp:attachment":[{"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=7116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=7116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=7116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}