Troubleshoot: M3 Users are not receiving output (Part 2)

Explanation: Users are complaining that their submitted jobs in M3 are not being received in their inboxes.

Problem Diagnosis

  1. Open MNS206 (M3 Output. Manage per Job)
  2. Change the Sorting order to 6-Output Status
  3. Type SND into the Sts column and type the date into the Ent dt column
  4. Press Enter

You now have a list of jobs that have the status SND (Sent) which means they have been sent but not saved or received by M3 – they have a status of SAV when they are successfully received by M3. Figure 1 indicates a sample job with SND.

1
Figure 1: A submitted job with status SND

Problem: The problem is with M3. You need to contact your M3 administrators and ask them to view its performance. They should especially check if any autojobs need to be restarted.

Once M3 has been fixed, all jobs with status SND will now automatically begin to hit StreamServe and produce output for users.

You do not need to resend jobs! 

You should monitor all traffic for a while and constantly refresh MNS206 to see jobs change status from SND to SAV (Sent & Saved).

Troubleshoot: M3 Users are not receiving output (Part 1)

Scenario: Users are complaining that their submitted jobs in M3 are not being received in their inboxes.

Problem Diagnosis:

  1. Open MNS206 (M3 Output. Manage per Job)
  2. Change the Sorting order to 6-Output Status
  3. Type MSG into the Sts column and type the date into the Ent dt column
  4. Press Enter

You now have a list of jobs that have the status MSG (Error Detected) – these jobs were sent during the downtime. Figure 1 indicates a sample job with MSG. Now You must find out what error has been detected.

50
Figure 1: A submitted job at status MSG
  1. Right-click on one of the MSG jobs and select Display
    1. The E panel is triggered
  2. The Message is CR_0025 and the description tells you that the server is not responding –  Figure 2 displays these details
49
Figure 2: Job error message onn MNS206/E panel

Problem: The problem is with StreamServe. The Control Center service is no longer running so it needs to be restarted.

Solution: 

  1. Click back to return to MNS206
  2. Open Control Center – the service will not be running
  3. Start the service

All jobs with status MSG will now automatically begin to hit StreamServe and produce output for users.

You do not need to resend jobs! 

You should monitor all traffic for a while and constantly refresh MNS206 to see jobs change status from MSG to SAV (Sent & Saved).

How to Easily Improve Traceability via M3 and your Delivery Note

Scenario: The Quality Department have informed you that they want the trailer number pirnted on every delivery note from now on however, the despatcher will only find out the trailer number at the time of loading.

For the solution I will use the Ext tracking no: textbox in the MWS410/F panel.

Solution Part 1: StreamServe

  1. Open the PageOut and add a label to the header section of your delivery note
  2. Enter the following text into the label: Trailer Number
  3. Drag the field AHOQETRN from the Field folder in the Message window and place it opposite (or beneath) the label Trailer Number
    1. If you have multiple pages you need to complete this step for each page
  4. Export and deploy the project

Solution Part 2: M3

  1. Open MWS410 (Delivery. Open Toolbox)
  2. Right-click on the delivery that you are currently despatching and select Change
  3. The panel MWS410/E opens however, you need to click Next (or hit Enter) to open panel F
  4. In the highlighted textbox in Figure 1, enter the trailer number which is being used for the despatch and click Next.
  5. Click the Back button until you return to MWS410 and proceed with the despatch as normal.

48
Figure 1: Snapshot of MWS410/F
When the Delivery Note is generated it will display the trailer number used for the despatch.

 

 

How to control the display of a label based on the value of a spool-field

SCENARIO: Some of your customers require their VAT number to be displayed on the invoice document. Your M3 customer master file only has the VAT number for several customers however you do not want to have the label VAT Number appearing with no accompanying value on an invoice.

  1. Open the OIS1990H event and transform the spool-field 0HWYVRNO into a variable 
  2. Open the PageOut and insert a Static Text object (this will be your label) to your canvas
  3. Rename the label to VAT Number
  4. In the Message window, collapse the Variable folder and drag the variable $0HWYVRNO to your canvasto the right/below of the label.
34
Figure 1: The Variable folder on the PageOut canvas
  1. Right-click on the label and select Edit Script…
  2. Insert the following code:

    if ($0HWYVRNO = “”) {
    skip();
    }
    else {
    {}
    }

The label VAT Number will now only appear if a value exists for the spool-field 0HWYVRNO. If the spool-field 0HWYVRNO value is blank then the label will be skipped (i.e. not appear).

Export and deploy and test!

Troubleshoot: Control Center producing the error: ‘Fatal error: portx spool=connector (port/printserver)’

Explanation: You are probably trying to create a new output connector in the Platform and you are using the connector type Spool and you are encountering this error. This is because you have not entered % into the To property – see Figure 1

33
Figure 1: Missing To property value

 

  1. Open the Platform
  2. Right-click on the new Output Connector and select Settings…
  3. From the Selected layer dropdown select Production (Physical)
  4. Make sure your Connector Type is Spool
  5. Enter % as the To property value
  6. Click OK

Export, deploy and test!

Troubleshoot: Control Center producing an ‘Fatal error: args start.arg(2:No such file or directory)’ error

Explanation: The first time you deployed an exported project in Control Center you did not check the Include argument file in export checkbox

The very first time you export a project you must check the Include argument file in export checkbox so that the start.arg file is created in the Working Directory

Figure 1 displays the checkbox to check:

32
Figure 1

Export, deploy and test!