Workbench Training

1. Workbench Training Learning to use the Workbench. Department of Public Welfare Information Systems Application Development and Delivery

2. Introduction • Workbench Background • Maintenance Teams use many utilities in their day to day development activities. • These utilities have their limitations. • They did not provide for any type of version control. • They were limited to their teams use.

3. Agenda • This presentation will cover the following topics: • Overview • Terminology • Interface • Administration • Main Menu • Compile • Screens • ATMS • Reports

4. Common Procedures After a brief overview of the workbench and the screens. There will be a walk through of the following common steps: • Registration • Checkout • Compiling • Checkin • Migration • Screens

5. Overview • The workbench provides a solution that is independent of an application and dynamic enough for future changes. • The following slides will provide enough background to understand the development procedures and how to do them utilizing the workbench.

6. Terminology • Environment: A defined domain for the execution of Software. • Registration: A profile of the software. • Repository: A master copy of the software. • Compile: Executing the necessary system utilities to create an executable. • Migration: Transfer of source from the repository to a specified environment.

7. Interface • White text is display only • Blue fields are data entry fields. • Green fields are transmit positions.

8. Common Screen Fields Registration is the process of adding the unique information for a program, proc, screen or environment Version control is the process of checkin or checkout for the purpose of identifying work in progress and keeping source versions. Migration refers to the transfer of programs, procs or screens from the workbench to a target environment

9. Common Screen Fields Create or Add provides a blank screen for data entry of the specific attributes. Create from will use the attributes for the name prior to the transmit position to retrieve the attributes and populate the screen for the new element. The attributes for the program, proc, screen or environment are retrieved and populated on the screen for review only The changes to registration information is logged. This menu option retrieves the history of those changes. The attributes for the program, proc, screen or environment are retrieved and populated on the screen for change

10. Common Screen Fields The program, proc or screen is copied from the workbench (if it exists) to the developers work file for change. It is then flagged as checked out. No other user can then check it out. The program, proc or screen is copied to the workbench, from the developers work file. It is then flagged as checked in. The checkin/checkout process creates a history, this menu option will display the history.

11. Common Screen Fields This is used to transfer a proc or screen from the workbench repository to a selected environment The history of migrations for the entered program, proc or screen

12. Function Keys • Depress F1 after positioning the cursor on any field for help on that field. • Depress F3 for a description of any screen • Depress F8 on any screen to terminate that screen. If on a menu, the program will terminate • Depress F2 on the BWBS16 screen to create a quick file of the source listed during that process.

13. Workbench Administration • Severely Limited individual Access • Define Environments • Define Users • Delete PROCS/Programs • Pack Files

14. Administration continued Environments contain the information that makes the environment unique. Generally these attributes are used for compiling and migration. Workbench users are required to be registered. This can be done by any workbench administrator or the user can register them self. This is used for security.

15. User Administration The only required information on this screen is the name. The rest is optional. The WB Admin, Screen Admin and Version Control Admin fields are only available to WB Administrators.

16. User Environment Access Enter a Y to give the user rights to that environment for: “G” - Programs “P” - PROCS “S” - Screens The environments are listed.

17. Environment Selection Environments are listed based on the user’s registration privileges . Enter the number of the environment that you want to select For example, enter 1 to select C Development DEVDMS . This screen is displayed whenever a selection of an environment is required during compiling, migration or application registration.

18. Environment Registration This screen contains the definition for an environment. Refer to the reference manual or use F1 for the values to enter in each field.

19. Environment Compile Edits This field is the value that needs changed To. The ~ (tilde) is a wild card. To limit the location of the change in the source. The first example limits the change to columns 1 through 7. During the compile process, the edits entered on this screen are applied to the source prior to compiling. This field is the value that needs changed from. The ~ (tilde) is a wild card.

20. Workbench Main Menu • All users have access • Check Out/In programs and PROCS • Program/PROC registration • PROC Migration

21. Main Menu To be presented with a blank screen to enter multiple programs or PROCS, place an X in this field and leave name/quick blank Enter the name of the program or proc that you want to take action on. To access a change number other than the most current, enter the change number here for migrations or checkout/ checkin. To view the source in the workbench repository. This bypasses the need to copy from the workbench and open in your favorite editor Enter the name of the quick file that you want to use. This is used instead of an individual name or multiple. Some online programs do pass off to explicit transactions. To change these to match the target environment during compiling, enter on the screen displayed when transmitting from here.

22. Check out Enter X to check out the source. Enter X to simply copy the source from the workbench repository. Enter the work file name that you want to have the source placed in.

23. Check In Enter X to undo/cancel a checkout. The workbench is set to “not” checked out and the history of the checkout is removed. Enter X to do a check-in. The workbench is set to “not” checked out and the history of the checkout is updated to reflect the check-in. The source is copied from the specified work file and placed in the workbench repository Enter the work file that the source is located to be checked in.

24. Program Registration This screen contains the definition for a program. Refer to the reference manual or use F1 for the values to enter in each field.

25. Transaction Mappings Enter the transactions that you want changed when compiling for any environment EXCEPT production.

26. PROC Registration This screen contains the definition for a proc. Refer to the reference manual or use F1 for the values to enter in each field.

27. Compiler Menu • All users have access • Compile programs for development • Compile programs for migration

28. To compile from a library other than the work bench repository, enter the qualifier and filename here. Compiler To recompile a program in a specific environment, enter Y here. To display a blank screen to enter multiple programs, transmit from here. To display a search screen to match on specific attributes (i.e., sub program), transmit from here To use a quick file, enter the name and transmit from here. To do a mass compile of all programs in the file specified above.

29. A sample quick file: @DATA,IQ IMD*MYQUICK. QUICK CF095R QUICK CF140R @EOF Sample Quick File

30. Compiler Options This screen contains the options and files to use for compiling. Refer to the reference manual or use F1 for the values to enter in each field.

31. Screens Menu • Limited access • Check Out/In screens • Screen registration • Screen Migration • Generate WS • Print Screen • View Screen

32. Screens To take action on a previous change number, enter here. Enter the screen number that you wish to take action on. To generate Working Storage (WS) , print or view from a specific environment, enter X here. To generate WS, print or view the current screen in the workbench, enter X here. To generate a DPS Screen print, transmit from here. To generate working storage, transmit from here. To view the screen, transmit from here. Migration for screens includes loading the Omnibus from the workbench and generating the working storage

33. Screen Checkout Enter X to checkout Enter the work file to copy the omnibus element to.

34. Screen Checkin To undo/cancel a checkout, enter X here Enter the file to check in the omnibus from.

35. Screen Registration This screen contains the registration for screens. Refer to the reference manual or use F1 for the values to enter in each field.

36. ATMS Menu • Limited access • Migrate an ATMS Quick File

37. ATMS Menu Enter ATMS file imported from ATS. Enter Desired Options. You may enter the target environments so BWBS09 is not used

38. Reports Menu • Access restricted to registered users • Refer to the Workbench Reference manual for report samples.

39. Reports When requesting a CO/CI report, you can limit the report by dates in these fields When requesting a CO/CI report, you can limit the report to a specific userid When requesting a CO/CI report, you can limit the report to just PROCS, programs or screens. Enter a screen number to get the environment summary report Enter a proc or program name for an environment summary report. Enter a program name for a program summary report

40. Registration Walk Through The registration process is similar for programs, PROCS, screens and environments. For the next couple of slides, there will be a demonstration of how to register a program. PRDEMO is a DPS, DMS, UCOB Program for MYAP. We begin by entering the Main Menu

41. Registration Walk Through Enter the program name Tab to the Add Program field and transmit

42. Registration Continued You are then presented with a blank screen, except for the program name.

43. Registration Continued Enter X for UCOB, DPS and DMS. Enter the subschema name. The keyword CIS is basically added as comment to state that this is a CIS transaction, hit transmit. Without error, you will return to the menu.

44. Check Out Walk Through The check out process is similar for programs, PROCS, screens and environments. For the next couple of slides, there will be a demonstration of how to check out a program. PRDEMO is the program we registered previously. We begin by entering the Main Menu

45. Check Out Walk Through Enter the program name Tab to the Check Out field and transmit

46. Check Out Enter X to Check Out. Enter the work file to copy the source to. In a new program, proc, etc, no copy will take place Since this is a new program, there is no source in the WB Repository to copy out to the work file.

47. History of Check Out The program is now checked out. Here it is reflected in the history.

48. Compile Walk Through The compile process is used to create relocateables, Object-Modules, ZOOM or absolutes based on the program registration. For the next couple of slides, there will be a demonstration of how to compile a program. PRDEMO is the program we registered previously. We begin by entering the Compile Menu:

49. Compile Menu Since we are developing, enter the work file name here Enter the program name here Transmit from here

50. Environment Selection Environments are listed based on the user’s registration privileges . This screen is displayed whenever a selection of an environment is required during compiling, migration or application registration. Enter the number of the environment that you want to select For example, enter 1 to select C Development DEVDMS .