For all users who are authorized to use the item.
For items which cannot be maintained such as items in a production GIL or items with a release status different from "1" in a release-controlled system.

To view an item on the "List of GIL items" panel type "V" in the "Act." column left of it and press the Enter key.

Note: "V" is the default value of language tailoring parameter LINVIEW.

Creating new GIL items using models (PN90817)

To select an item on the List of GIL Items panel as model for creation of a new GIL item type "CWM" (create with model) in the "Act." column left of it and press the Enter key. A prompt panel made up by ATD "xxxSGILMOD" (where xxx is the language code of the session) is displayed where the user needs to specify the name of the new GIL item. Pressing Enter displays the applicable GIL item maintenance panel.

This function is of special interest for installations with versioning control. The administrator can select outdated versions of a GIL item as model for his new GIL item.

Note: "CWM" is the default value of language tailoring parameter LINCWM.

Interaction between ATD and ATD-PDP

If during execution of an ATD a PDP is called and returns a SIB_MSG_CODE of 256, the

Panel "Application-Parameter Prompting" is not displayed before invocation of the ATD target application
SIB control block returned from the PDP is routed to the ATD target application Because in this situation the SIB returned from the PDP is not checked the PDP can build a completely new SIB control block for invocation of the target application.
Panel "Application-Parameter Prompting" is not displayed after return from the ATD target application unless parameter DXBZPROMPT has been defined in the ATD with a value of 1.

User parameter DXBDATE (PQ01523)

The user parameter DXBDATE is automatically resolved with today's date if no value has been assigned by the user. If ASF is operated in 7*24 mode (7 days, 24 hours), DXBDATE is automatically updated with today's date if the system date has changed between the last request resolving DXBDATE and the current one.

Note: Customers who are assigning a future date to DXBDATE and who are keeping ASF sessions active beyond the end of the day have to be aware that DXBDATE is updated as described above.

Invoking ASF from a front-end application

Parameters passed in the SIB from an application that invokes ASF for display of a menu are saved. For each subsequent invocation of an ATD these parameters are retrieved and merged with the ATD parameters. Processing is similar to the situation where the ATD would have been invoked directly from the front-end application.

Attributes of SIB parameters received upon invocation of ASF are honored upon merging during ATD execution if the new SIB parameter attribute SIB_PRM_ATTR_MERGE has been set.

DB2-dependent administration enhancements

The functions described in this chapter require ASF to run with DB2 and working in an ASF environment that has been tailored to work with DB2.

Handling of the release name in GIL items

In a release-controlled system a release name is the proper means to identify a group of GIL items that belong together and are to be treated as a group when being transferred from test into production.

The following tools are important when working with release names:

Default release name in the user profile (PN90817)

The release-control settings panel in the user profile maintenance has been enhanced to define a user specific default release name.

Using fast path command xxxRLSNAM (xxx is language code of the session) the release control settings panel is displayed to change the default release name in the user profile. A change of the default release name will become active at once.

Assigning a release name to a GIL item (PN90817)

In a release-controlled system an administrator can change the release name of a GIL item from the List of GIL items panel without stepping into the GIL item maintenance. To assign a release name type "ARN" left of the selected item and press the Enter key. The release name of the item is set to the default value defined in the user profile.

Note: The default release name is shown right of the test level notification on the List of GIL Items panel.

The base tailoring parameter SETRELN controls the setting of the release name when copying an item from the production GIL into the test GIL using action "DEV" on the List of GIL Items panel: The release name of the new item

Is set to the value of the copied item if SETRELN has a value of 0.
Is set to blank if SETRELN has a value of 1.
Is set to the default release name as defined in the user profile if SETRELN has a value of 2.

Note: "ARN" is the default value of language tailoring parameter LINARN.

Collecting messages during integration in release-controlled systems (PN87668)

When integration fails checking of GIL items is now continued to find all errors which would impede the integration of the system. For each error a message is collected in an information item that can be viewed after the integration. The name of the information item obtaining the messages is determined as follows:

DXBRCID is a parameter name in the ATD used for integration (such as ENUSINTEGRATE) and contains a valid GIL item name. ASF takes the value of DXBRCID as GIL item name.
Otherwise the name of the information item is built as concatenation of the user id of the user performing the integration function and the characters "INTEGRAT".

The information item is always built as a private item. The item description contains the date and time when the integration function has been invoked.

Note: Checking for errors is not continued if integration of the system is not possible due to one of the following two reasons:

The system is already integrated.
The check for items for which testing has not completed is activated, and this check fails.

Integration of GIL items in a release-controlled system (PQ06855)

The integration of GIL items (initiated by ATD "ENUSINTEGRATE") is possible even if other items have been integrated before and are still on integration level with a release status of '9'. As a result, both the previously integrated items and the items being newly integrated are on integration level with a release status of '9'. If the integration fails because the integration criteria are not met, the previously integrated items remain on integration level.

Sort sequence of lists of database items (PN90818)

When requesting online display of a list of items from the GIL, SLL, CLL, document cabinet, or text cabinet a user can now specify sort criteria.

Specifying sort criteria

To specify sort criteria you need to define reserved parameter DXBLSORT in the parameter list of the ATD used to call up the database list.

DXBLSORT obtains the name of the list search parameter representing the column you want the list get sorted by. For example, if you want to get the list sorted by

Item name, specify DXBLSELNAM as value of DXBLSORT.
The name of the last modifying user, specify DXBLMODUSR as value of DXBLSORT.

The following columns can be selected for sorting:

Columns valid for all types of database lists (GIL, SLL, CLL, document cabinet, text cabinet)

DXBLSELNAM
Item name
DXBLMODUSR
Name of last modifying user
DXBLMODDAT
Date of last modification
Columns valid for lists of GIL items
- All types of GIL items
  
  DXBLRELNAM
  Release name
  DXBLRELSTA
  Release status
  DXBLRELDAT
  Release date
  DXBLREFDAT
  Reference date
- All types of GIL items except for PDRs
  
  DXBLOWNER
  Owner name
  DXBLITMTYP
  Item type
  DXBLSTATUS
  Item Status
- Lists of ATD items only
  
  DXBLPGMNAM
  Name of ATD target program
  DXBLPDPNAM
  Name of PDP
Columns valid for lists of document (text) cabinet items

DXBLOWNER
Owner name
DXBLREFDAT
Reference date

Specifying multiple sort criteria

To combine sorting according to several columns you can define up to three occurrences of parameter DXBLSORT in the ATD used to call up the online database list. The sort sequence is determined by combining the values of the DXBLSORT parameter entries in a top-down sequence.

How to request ascending or descending sort

To request ascending sorting for a specific column append an 'A' to the value in DXBLSORT, separated by a comma. To request descending sorting for a specific column append an 'D' to the value in DXBLSORT, separated by a comma. For example:

For ascending sorting of the "Item name" column specify "DXBLSELNAM,A" as value of the DXBLSORT parameter entry.
For descending sorting of the "Owner" column specify "DXBLOWNER,D" as value of the DXBLSORT parameter entry.

Note: If neither 'A' nor 'D' has been specified, 'D' is assumed as default.

Sample ATDs containing DXBLSORT parameter entries

The following sample ATDs contain entries of parameter DXBLSORT. It is recommended to load them into your GIL database:

ATDs to display the List of GIL Items panel
- xxxSLGILNP1DB2
- xxxSLGILNP2DB2
- xxxSLGILNP3DB2
- xxxSLGILNP4DB2
- xxxSLGILNP5DB2
- xxxSLGILNP6DB2
- xxxSLGILNP7DB2
- xxxSLGILPDB2
ATD to display the List of CLL Items panel
- xxxSLCLLDB2
ATD to display the List of SLL Items panel
- xxxSLSLLDB2
ATD to display the List of Document Cabinet Items panel
- xxxSLDCDB2
- xxxSLDCADB2
ATD to display the List of Text Cabinet Items panel
- xxxSLTCDB2
- xxxSLTCADB2

Note: (xxx is the language code of the session)

DB2-like wildcards for extended generic search (PN90818)

When requesting online display of a list of items from the GIL, SLL, CLL, document cabinet, or text cabinet a user can now use DB2-like wildcards for extended generic search.

The selection of the items to be displayed can become more precise by inserting arbitrary strings and/or single arbitrary characters into the search strings of the following selection criteria:

Generic item name
Last modifying user
Program name
PDP name
Item owner
Release name

Note: The asterisk (*) represents a string of zero or more arbitrary characters. The sign defined by the tailoring parameter SINARBCH represents a single arbitrary character. Default is the percent sign (%). Both symbols can be entered multiple times and at any position within the search string.

Examples:

The search string "A*B" entered into the selection criterion "Generic item name" finds all items with a name beginning with "A", ending with "B" and no or any unknown characters in between. The search string "A%%B" entered into the selection criterion "Release name" finds all items with a release name of four characters length, beginning with "A", second and third character unknown and last character "B".

DC Feature enhancements

Usability enhancements (PQ09333)

The F-key "Main Menu" is now also available on the following panels:

"Application-Parameter Prompting"
DC Feature panels:
- "Paragraph Selection"
- "Document-Parameter Prompting"
- "Document-Composition Termination"

If ASF has been invoked from a customer program, the F-key "Exit" is available on the following panels:

"Menu" panels
"Information" panels
"Application-Parameter Prompting"
DC Feature panels:
- "Paragraph Selection"
- "Document-Parameter Prompting
- "Document-Composition Termination"

Security concept for CLL and SLL (non-DB2-environment)

The user profile maintenance has been enhanced to grant project-based maintenance authorization for SLL and CLL items (LRRs). However, this new authorization does only apply for those SLL (CLL) items having an owner or getting an owner.

An LRR owner being assigned to an LRR by

Exit program FSNLCME
The interface area for FSNLCME has been enhanced accordingly with the new field LTE_LRR_OWNER.
Parameter DXBLRROWNR passed to ASF upon invocation with SIB type 1 for function LCF.

must be the name of a project where the user has SLL/CLL maintenance competence.

SLL (CLL) items having an owner

Do not show up on the online SLL (CLL) list if the user is not assigned to the project (= LRR owner)
Cannot be deleted or resumed for document composition by users not having SLL/CLL maintenance authorization in the owning project.

When requesting display of an online SLL (CLL) list you can specify a fully-qualified or generic project name using parameter DXBLOWNER in the parameter-list of the ATD (for example ENUSLSLL or ENUSLCLL).

Record prefix for CLL items

LRRs are written to the CLL with a timestamp as record key unless a record-key prefix has been specified by

Exit program FSNLCME
The interface area for FSNLCME has been enhanced accordingly with the new field LTE_CLL_PREF
Parameter DXBCLLPREF passed to ASF upon invocation with SIB type 1 for function LCF.

This function needs to be considered in conjunction with the enhancement of selective export from the CLL introduced by APAR PQ09285.

New functions of exit program FSNLCME

The interface control block for exit program FSNLCME has been enhanced to support

Suppression of the display of specific "Action" and "Continuation" values on the Document-Composition Termination panel.
A CLL record-key prefix
An LRR owner
Call of FSNLCME for input validation and adaptation before input check performed by ASF
A value of '2' set by FSNLCME in the field LTE_CALL_INP_EX of the interface control block during the first call of the exit triggers a follow-on call during processing of the panel input before ASF performs a check of the input data.

New functions of exit program FSNITPE (PQ06567, PQ09287)

The description of user exit program FSNITPE in APAR PQ06794 and the following documentation change will be added to the manual 'Application Programming Interfaces'. User exit FSNITPE supports

Highlighting of one line in error
Positioning of the cursor on any line.

The following fields have been added to the communication area for exit FSNITPE:

ITP_HLIGHT_LINE: Contains the number of the line which should be highlighted on return from FSNITPE exit. The number must be less or equal than the maximum number of lines passed to the exit (ITP_SCREEN_LINES).
ITP_CURSOR_LINE: Contains the number of the line on which the cursor should be positioned. The number must be less or equal than the maximum number of lines passed to the exit (ITP_SCREEN_LINES).
ITP_CURSOR_COL: Contains the column within the line passed in the field ITP_CURSOR_LINE.
ITP_ICA_PTR: Pointer to the ASF internal communication area FSNICA.

Compression of LRRs upon writing to CLL (PQ04719)

When the LRR being created during document composition is written to the CLL it will be compressed, if

The base tailoring parameter LRRCMPR has been set to 1
ASF has been invoked with a SIB type 1 and reserved parameter DXBCMPRLRR has been passed in the SIB with a value of 1.
Parameter DXBCMPRLRR can be used to overwrite the setting of base tailoring parameter CMPRLRR.

Compression means that descriptions of standard paragraphs and parameter prompt texts are reduced to a length of 1. Under VSAM or DL/I the amount of DASD space claimed by an LRR on the CLL can be reduced significantly depending on the number of SPs and parameter references. When using DB2 for the CLL the number of fields containing one character padded with blanks rises significantly. This helps DB2-based compression programs to reduce the space claimed by the CLL.

Processing of DCF-imbeds in standard paragraphs (PQ03250)

DCF imbeds referenced in standard paragraphs (SP) are now honored regardless where the ".IM" control starts within a line of the SP.

The ASF Administration Guide, SH12-5936-02, Chapter 9, Batch formatting, will be updated with the following text:

If .im is used in a standard paragraph (SP) or in an individual text, Application Support Facility includes SPs from the GIL only if the control word is followed by the SP name and if

the control word starts in column 1 or
the control word starts anywhere else in the line and is directly preceded by the default control word separator ';'. The control word separator must not be changed.

Variables in the SP name are not resolved. The following .im control word is not processed but passed like other control words:

  .if &i = 1 .im doc2

However, if the document (e.g. doc2) is stored in the Document Library Facility (DLF), the imbed is processed correctly. If the name of the SP you want to include is longer than 8 characters, enclose the name in parentheses:

  .im (DXBSP8200)

Synchronous invocation of DCP (PQ09467)

Under CICS, ASF can now invoke a data-collection program (DCP) synchronously using an EXEC CICS LINK statement. This enables the DCP to prevent writing of a document to the CLL for collect printing.

The administrator defines the DCP to be called synchronously on the "Define Document Type - Header Data Part 2" panel. The value of the field "Invocation" right of the DCP name has to be set to 1.

Invocation of PDPs (PVPs) from FSNBTCH (PN87668)

Although FSNBTCH is running in 31-bit addressing mode, a parameter determination program (PDP) or a parameter verification program (PVP) called from FSNBTCH can now run in either 31-bit or 24-bit addressing mode. Switches of the addressing mode are automatically performed by FSNBTCH.

DW Feature enhancements

Compatible processing for ATDs with parameter DXBZPROC (PQ05882)

Migrated ATDs containing parameter DXBZPROC in their parameter list with a value of

4: Store document to DISOSS
5: Print and store document to DISOSS

are now supported. In difference to predecessor releases the document being composed is kept in the document cabinet.

User-defined title of Variable and Parameter Prompting panel (PQ08535)

To display the title of the ATD used to invoke the Document Writing feature as title of the Variable and Parameter Prompting panel, you need to define parameter DXBZDSCATD with a value of 1 in the parameter list of the ATD.

ASF session debug trace and DW/370 external trace (PQ07856)

If the ASF session debug trace has been activated for a specific user ID, the DW/370 external trace is not invoked automatically. To trigger writing of the DW/370 external trace, add the new parameter DXBZDWTRAC with a value of 1 to the parameter list of the ATD used for invocation of the DW feature.

Parameter	Value	Meaning
Parameter	DXBZDWTRAC	0	Do not invoke DW/370 trace automatically if ASF session debug trace has been turned on (Default)
1	DXBZDWTRAC	Invoke DW/370 trace automatically if ASF session debug trace has been turned on

New Tailoring Parameters

The new tailoring parameters having been introduced are described below in sections according to the tailoring structure.

Base Tailoring (FSNT000CI)

Feature-independent parameters

CURSMEN (PN92256)
ENVPROT (PQ09512)
NOMORE (PN92256)
NOPRTHD (PQ08725)
SETRELN (PN90817)

Table 1. Feature-independent base tailoring parameters

Parameter	Description	CICS	IMS
CURSMEN	0 Cursor on menus is initially displayed on the selection line 1 Cursor on menus is initially displayed on the command line 2 Display menu panels without selection field for menu options	x	x
ENVPROT	When a project administrator defines a new user ID, the Environment name field on the "Session Control Settings" panel in the user profile maintenance is protected The environment of the administrator also becomes the environment of the new user ID 0=No, 1=Yes	x	x
NOMORE	Suppress display of the "More" indicator: 0=No, 1=Yes	x	x
NOPRTHD	Print GIL items without the header information containing name of the item, user ID etc. 0=No, 1=Yes	x	x
SETRELN	Defines processing of the release name of a GIL item upon takeover from production to test in a release-controlled system. The release name 0 remains unchanged 1 is set to blank 2 is set to the user's default	x	x

Base tailoring parameters for the Document Composition Feature

LRRCMPR (PQ04719)

PRMREFR (PQ09514)

PROMLIN (PN87668)

Table 2. Base tailoring parameters for &docc.

Parameter	Description	CICS	IMS
LRRCMPR	Compress document-request record (LRR) upon writing to the CLL initiated by Request for collect print Utility FSNBTCH 0=No, 1=Yes	x	x
PRMREFR	Force refresh of user/system parameters when resuming document composition with function codes RLCF or SLCF. Refreshing 0 No 1 User parameters 2 System parameters 3 User and system parameters	x	x
PROMLIN	0 No action 1 Reduces the number of prompt lines on the Document-Parameter Prompting panel 2 Reduces the number of menu display lines by 1 3 Functions of 1 and 2	x	x

Base tailoring parameters for the Document Writing Feature

DWDOCPRF (PQ07549)
DWGLNPRT (PQ07549)

Table 3. Base tailoring parameters for the Document Writing Feature

Parameter	Default	Description
DWDOCPRF	MEMO	Prefix for system-generated document names. Value can be up to 8 characters long and is overwritten by user profile definition Note: The acronym ?UID? indicates that the session user ID is used as document prefix
DWGLNPRT	0	Use line print for GIL items rather than printing them with DW/370 0=NO, 1=YES

Environment Tailoring (FSNT100C/I)

BLRRNAME (PQ04411)

Parameter

Default	Description	CICS	IMS
BLRRNAME	FSNDBLRR	DBD name for BLRR data set. Support of different BLRR data when exporting different CLLs		x

Parameters for coexistence with OV/MVS

EABTXC (PN91553) (replacing tailoring parameter EABPREF)

Parameter	Default	Description	CICS	IMS
EABTXC	ENJ0	Default transaction code for switching into the Enterprise Address Book of OV/MVS	x

Language Tailoring (FSNTxxxe)

Note: ("xxx" is the language code such as "ENU" for English and "e" either is "C" for CICS or "I" for IMS).

SELCHAR (PN87668)
SINARBCH (PN90818)

Table 4. Language tailoring parameters

Parameter	Default	Description	CICS	IMS
SELCHAR	/	Character marking options in the GIL and UPL maintenance as selected	x	x
SINARBCH	%	Single arbitrary character for extended generic search in databases if DB2 is used	x	x

Line commands

LINARN (PN90817)
LINVIEW (PN87668)
LINCWM (PN90817)

Table 5. Line commands for database list panels

Parameter	Default	Description	CICS	IMS
LINARN	ARN	Line command to assign the user's default release name to the selected item on the List of GIL Items panel	x	x
LINCWM	CWM	Line command to select an item on the List of GIL Items panel as model for creation of a new GIL item	x	x

Utility enhancements

Enhancements for utility FSNBRUL (PQ07032, PQ07933)

Downloading/Deleting SLL items

The keyword LTDNAM allows to search for SLL items that have been created on basis of specific LTDs. With LTDNAM you can specify an LTD name, a list of LTD names, or a generic LTD name. The length of an LTD name may not exceed 16 characters.

In the Administration Guide, SH12-5936, Appendix C, paragraph "Request control statements for FSNBRUL", will be enhanced. The table showing the use of keywords in regard to the library being processed is enhanced as follows:

Keyword	Library
Keyword	GIL	UPL	Text cabinet	Document cabinet	SLL
LTDNAM	--	--	--	--	*
MODBEG	--	--	--	--	*
MODEND	--	--	--	--	*

LTDNAM (PQ07933): Specifies an LTD name, a list of LTD names, or a generic LTD name. The length of an LTD name may not exceed 16 characters. All LRRs generated by the specified LTD are processed.
MODBEG (PQ07032): Allows to search for all SLL items modified on or after that date. Syntax: MODBEG(YYYYMMDD)
MODEND (PQ07032): Allows to search for all SLL items modified before or on that date. Syntax: MODEND(YYYYMMDD)

Enhancements for utility FSNCEXPC/I (PQ09285)

The following new keywords can be specified to control the processing of FSNCEXPC (FSNCEXPI):

NODELETE

The LRRs exported from the CLL are not deleted and remain on the CLL. Example: NODELETE

ITNAM(value)

Specifies an LRR ID or a generic LRR ID. The length if the LRR ID may not exceed 16 characters. If the LRR ID is fully qualified, value has to have a length of 16 characters and be enclosed in apostrophes, if it contains a blank. If value is a generic LRR ID it must contain only one asterisk which has to be at the end of value.

Examples:

ITNAM('970612141212781 ')
the LRR with this ID is selected
ITNAM(970613*)
all LRRs with IDs starting with 970613 are selected

MODUSER(value)

Specifies a fully qualified user ID with a length of up to 8 characters.

Example:

MODUSER(ENUADM)

all LRRs which were generated by ENUADM are selected

OWNER(value)

specifies a fully qualified project name with a length of up to 8 characters which owns this LRR.

Example:

OWNER(DXBMAIN)

all LRRs which are owned by project DXBMAIN are selected

TOKB=(kbid) (PQ03247)

Specifies a code-page used for creation of the output data set FSNLRR. If TOKB is omitted a code-page value of 500 is assumed. The use of TOKB is recommended if the data set FSNLRR is processed by customer programs expecting the data of the BLRR records to be in a specific code-page. Otherwise TOKB can be omitted. For information on the supported code-page values, refer to "Adjusting the code-page table with FSNACPM" in appendix C.

Note: If TOKB is used with a code-page value different of 500, the keyword FROMKB with the same code-page value must be used for utility FSNBDCFC/I.

The keywords have to be inserted after the SYSIN DD statement. One keyword per line is allowed.

Note: With the exception of TOKB the keywords are not valid for Application Support Facility running with DB2.

Enhancements for utility FSNBTCHC/I (PQ05787)

New control keyword TOKB

The list of control statements for the utility FSNBTCH is enhanced with the following description:

TOKB=(kbid): Use control statement TOKB to identify the code-page of the BLRRs stored in output data set FSNLRR. If the control statement is omitted, TOKB=(500) is assumed. For information on the supported code-page values, refer to "Adjusting the code-page table with FSNACPM" in appendix C.

Note: If TOKB is used with a code-page value different of 500, the keyword FROMKB with the same code-page value must be used for utility FSNBDCFC/I.

Enhancements for utility FSNBDCFC/I (PQ09285)

New control keyword FROMKB

The list of control statements for the utility FSNBDCF is enhanced with the following description:

FROMKB=(kbid): Use control statement FROMKB to identify the code-page of the BLRRs stored in input data set FSNLRR. If the control statement is omitted, FROMKB=(500) is assumed.

Note: If control statement TOKB has been used with utility FSNCEXP, utility control statement FROMKB must be used with the same code-page value as specified in TOKB. For information on the supported code-page values, refer to "Adjusting the code-page table with FSNACPM" in appendix C.

Use of control keyword buffer (PQ04929)

The tuning of utility FSNBDCF has been redesigned to no longer consume main storage specified in the BUFFER control statement. It works as follows: When an SP is encountered for the first time, a macro is defined to DCF including the contents of this SP and the macro name is stored in ASF. When the same SP is encountered again in a following document the macro is just executed again.

The specification of control keyword BUFFER is no longer necessary to activate the tuning as described above.

If the output of utility FSNBDCF is split into separate parts and then submitted to DCF in separate steps it is possible that an execute macro statement is submitted without the macro being defined before. To avoid formatting errors in this case you can force to turn off the internal tuning by specifying control statement BUFFER SIZE(000K). BUFFER SIZE(000K) causes the definition of a macro every time an SP is encountered, thereby avoiding the problem described above.

Output statistics (PQ04626)

The following output statistics in FSNBDCF have been removed because the keyword BUFFER is no longer honored:

Maximum free space in buffer     : //////////
Minimum free space in buffer     : //////////
Resident GIL buffer usage count  : //////////
Resident GIL buffer add count    : //////////
Resident GIL buffer replace count: //////////
Resident GIL buffer purge count  : //////////

Enhancements for utility FSNLOADC/I (PQ09285)

It is no longer required to provide all input to FSNLOAD in code-page 500 and to run utility FSNACPM.

Keyword FROMKB=(kbid) can be used to identify the code-page of the input which is to be loaded. If the control statement is omitted, FROMKB=(500) is assumed. For information on the supported code-page values, refer to "Adjusting the code-page table with FSNACPM" on page 381.

Enhancements for utility FSNCF00C/I (PQ06891)

The command DCFCOPY forces utility FSNCF00C/I to provide the DCF input in a sequential file. The ASF Administration guide, SH12-5936-02, chapter 9, paragraph "Commands for continuous formatting" is updated with the following information:

DCFCOPY(YES»NO): This command writes the DCF input data stream into the sequential data set defined in the DCFIN DD statement. Each document is identified by a START and END line including its associated LRR key. The default is NO.

Coexistence with OV/MVS

The information below was published along with the following APARs: PN915553, PN92432, PQ04574, PQ05532, PQ07928, PQ08479, PQ09097.

Common user profile enrollment

The section "Enrolling user IDs in OfficeVision/MVS" will be enhanced with the list of the additional parameter entries for ATD ENUOVENROLL:

ATD parameters used for controlling of the enrollment in OV/MVS:

DXBENRLPS: The value of this parameter determines whether the user is enrolled in PS or not (0=No, 1=Yes).
DXBENRLCAL: The value of this parameter determines whether the user is enrolled in CAL or not (0=No, 1=Yes).
DXBENRLEAB: The value of this parameter determines whether the user is enrolled in EAB or not (0=No, 1=Yes).

ATD parameters used for enrollment in all components

DXBUPMNODE: The value of this parameter is mapped into the API field COMNODE. It determines the node ID of the user.
DXBUPMDEPT: The value of this parameter is mapped into the API field COMDEPT. It determines the department of the user.
DXBUPMPHON: The value of this parameter is mapped into the API field COMPHONE. It determines the phone number of the user.
DXBUPMJOB: The value of this parameter is mapped into the API field COMJOB. It determines the job title of the user.
DXBUPMLOC: The value of this parameter is mapped into the API field COMLOC. It determines the location of the user.

ATD parameters used for enrollment in the Enterprise Address Book (EAB):

DXBENJPREF: The value of this parameter is mapped into the API field ENJPREFIX. It determines the title of the user.
DXBENJPNAM: The value of this parameter is mapped into the API field ENJPNAME. It determines the preferred name of the user.
DXBENJMNAM: The value of this parameter is mapped into the API field ENJMNAME. It determines the middle name of the user.
DXBENJSUFF: The value of this parameter is mapped into the API field ENJSUFFIX. It determines the suffix.
DXBENJJDES: The value of this parameter is mapped into the API field ENJJDESCR. It determines the job description of the user.
DXBENJCMPN: The value of this parameter is mapped into the API field ENJCMPNY. It determines the company name.
DXBENJDIVI: The value of this parameter is mapped into the API field ENJDIVISN. It determines the division.
DXBENJATEL: The value of this parameter is mapped into the API field ENJATEL. It determines the alternate telephone number.
DXBENJFAX: The value of this parameter is mapped into the API field ENJFAX. It determines the fax number.
DXBENJBLDG: The value of this parameter is mapped into the API field ENJBLDG. It determines the building.
DXBENJOFF: The value of this parameter is mapped into the API field ENJOFF. It determines the office number.
DXBENJINT1: The value of this parameter is mapped into the API field ENJNTM1. It determines the first part of an internal mailing address.
DXBENJINT2: The value of this parameter is mapped into the API field ENJNTM2. It determines the first part of an internal mailing address.
DXBENJINT3: The value of this parameter is mapped into the API field ENJNTM3. It determines the first part of an internal mailing address.
DXBENJINT4: The value of this parameter is mapped into the API field ENJNTM4. It determines the first part of an internal mailing address.
DXBENJNICK: The value of this parameter is mapped into the API field ENJNICK. It determines the shared nickname of the user in EAB.

ATD parameters used for enrollment in DISOSS

Enrollment in the DISOSS-HUD is performed using the product HUPDATE from TBS Software, Canada.

DXBENRLHUP

0/1 specifying whether enrollment via HUPDATE is required.

DXBHPMSG

obtaining the HUPDATE return message

DXBODPWD

optional overwriting of the DISOSS password

If the DISOSS password has been specified in the ASF UPR it will be taken from there. The external name will be built from the full user name specified in the ASF UPR It can be overwritten by parameters

DXBUPMFNAM (first name) and
DXBUPMLNAM (last name)

in ATD ENUOVENROLL.

DXBTHPFNAM

determines how the external name is to be built from FNAM and LNAM

DXBTHPTYPE

Default value set by program is API. This parameter allows to overwrite the DISOSS user type.

DXBOMODUID

DISOSS-HUP model user ID - mandatory information

If no parameter value has been spefified here, the parameter value if taken from existing ENUOVENROLL parameter DXBUPMMUID

DXBOMODNID

DISOSS-HUP model node ID - mandatory information

If this parameter is not specified I take the default node ID from ASF tailoring.

Processing of the full user name

The coupled user profile maintenance between ASF and OV/MVS has been enhanced as follows: A full user name having been specified for a new user ID on the "General Profile Settings" panel in ASF is split into two pieces. These pieces are merged into the parameters DXBUPMFNAM and DXBUPMLNAM of ATD ENUOVENROLL resulting in a pre-filling of the prompt fields for first and last name on the ENUOVENROLL prompt panel.

Note: The separation of the full user name into first name and last name may need correction which can be applied on the ENUOVENROLL prompt panel before enrolling the user.

The value specified for the last name (in parameter DXBUPMLNAM) is checked for characters not valid in Calendar:

Period "."
Underscore "_"
Asterisk "*".

EAB department verification (PQ07932)

If a user is to be enrolled in EAB, a department name having been specified is checked against the EAB department table.

Deleting user IDs in OV/MVS

For common deletion of user IDs in ASF and OV/MVS the ASF panel "List of User Profiles" is the right place to start with. To implement connection between this panel and the OV/MVS admin API, the ATD used to invoke the List of User Profiles" panel (for example, ENUSLUPL) needs to contain parameter DXBUPMATDN containing the name of the ATD triggering the admin API (for example, ENUOVENROLL). ATD ENUOVENROLL can be used to trigger both enrollment and deletion of user IDs in OV/MVS. However, for ease of use it is recommended to work with a separate ATD when requesting deletion of user IDs from the "List of User Profiles" panel in ASF. The delete request does not require all details necessary for enrollment. For working with the List of User Profiles panel it is recommended to

Copy ATD ENUOVDELETE
Modify the copy to the needs of the local installation
Define the name of the copy as value of parameter DXBUPMATDN in the ATD used to call up the List of User Profiles panel, for example ENUSLUPL (or a copy)

Invocation of CICS programs in OV/MVS environment using ATDs

CICS programs like CLASY from TBS being invoked with an ATD need to know the CICS transaction codes of the OV/MVS components Personal Services (PS), Calendar (CAL), and Enterprise Address Book (EAB). The standard interface block (SIB) ASF passes to an application when executing an ATD has been enhanced to convey these transaction codes. For details of the SIB field names refer to the delivered PL/I copy book FSNSIB in installation library AFSNMAC0.

Coexistence with OV/PF - tailoring adaptations (PN91553, PQ04574)

For coexistence between ASF and OV/PF the following adaptations of the tailoring for both ASF and OV/PF are required:

ASF environment tailoring FSNT100C:
To use the alternate Address Book of OV/PF you need to define "BOVB" as value of tailoring parameter EABTXC.
OV/PF tailoring
- BOVDEF0
  - Tailoring parameter OV_ASF_COEX has to be set to 1.
  - Tailoring parameter OV_TCTUA_OFFSET has to be calculated as follows:
    value specified in ASF base tailoring parameter TCTDISP + 16
- BOVDEF1
  - Tailoring parameter CA_ASF_COEX has to be set to 1.
  - Tailoring parameter CA_TCTUA_OFFSET has to be calculated as follows:
    value specified in ASF base tailoring parameter TCTDISP + 16

Coexistence with OV/PF note editor

The fast path commands invoking the OV/PF note editor are made up by ASF ATDs. In OV/MVS standalone these ATDs are invoking the OV/PF program BOVNE10. In coexistence with ASF

These ATDs are replaced and call Document Writing feature program FSNASF3.
Control parameter DXBZREQT has a value of 09.
The ATD parameter lists are different.

The new request type 09 is only valid if base tailoring parameter OVCOEX has been set to 1 thereby indicating that ASF runs in coexistence with OV/MVS.

Note: The following functions will be implemented with follow-on APARS:

Support for NOTEEAB command
Put documents from a PS-initiated DW/370 session into the Document Cabinet

Application Support Facility