To Execute this Example

LANSA

To Execute this Example
Tier Aware Reporting The Things that Make Up this Example

Local Execution (No Remote Tiers)

To use this example with no remote tiers (ie: as a standalone application):
  • Execute the Tier Configurator VL_SAM134 and make sure that you have this tier configuration:
SystemValid Connection Details Are Required APPL Tier DATA TierPRINT TierBATCH Tier
Default ClientNoSystem ItselfSystem Itself System ItselfSystem Itself
Default iSeriesNoSystem ItselfSystem ItselfSystem ItselfSystem Itself

  • Close the Tier Configurator VL_SAM134.
  • Now execute form VL_SAM139 and try printing the report immediately and via the queue.
  • In this configuration all reporting activities are performed on your local system.
Thick Report Execution (Remote DATA Tier)

To use this example with a remote DATA tier (ie: as a thick report application)
  • Execute the Tier Configurator VL_SAM134 and make sure that you have this tier configuration:
SystemValid Connection Details Are Required APPL Tier DATA TierPRINT TierBATCH Tier
Default ClientNoSystem ItselfDefault iSeriesSystem ItselfSystem Itself
Default iSeriesYes System ItselfSystem ItselfSystem ItselfSystem Itself

  • Close the Tier Configurator VL_SAM134.
  • Now execute form VL_SAM139 and try printing the report immediately and via the queue.
  • In this configuration all reporting activities (immediate or queued) are being performed on your local system, but DBMS details are being read from the remote DATA tier.
Thin Report Execution (Remote PRINT and DATA Tiers)

To use this example with a remote PRINT and a remote DATA tier (ie: as a thin reporting application)
  • Execute the Tier Configurator VL_SAM134 and make sure that you have this tier configuration:
SystemValid Connection Details Are Required APPL Tier DATA TierPRINT TierBATCH Tier
Default ClientNoSystem ItselfDefault iSeriesDefault iSeriesSystem Itself
Default iSeriesYes System ItselfSystem ItselfSystem ItselfSystem Itself

  • Close the Tier Configurator VL_SAM134.
  • Now execute form VL_SAM139 and try printing the report immediately and via the queue.
  • In this configuration all reporting activities are performed on the PRINT tier. In immediate mode VL_SAM139 actually calls VSAM138 on the PRINT tier and then waits until it finishes producing the report. In queued mode it submits VSAM138 onto the PRINT tier for later execution.