CN116339806A

CN116339806A - Production processing method and device for TWS transition version

Info

Publication number: CN116339806A
Application number: CN202310175911.7A
Authority: CN
Inventors: 张娟; 何宏烨
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2023-02-28
Filing date: 2023-02-28
Publication date: 2023-06-27

Abstract

The invention provides a method and a device for producing TWS transition versions, and relates to the technical field of data processing, wherein the method comprises the following steps: acquiring a transition version scheduling file of the TWS, checking the transition version scheduling file according to preset conditions, and releasing the transition version scheduling file after the checking is passed; analyzing the transition version scheduling file to obtain script parameter information; reading a transition version script template of the TWS, and generating a TWS transition version script according to the script parameter information and the transition version script template; obtaining a script effective time point, a script data list and a catalog of an operation entity according to the TWS transition version script, and checking the TWS transition version script; after the verification is passed, loading TWS transition version resources according to the TWS transition version script; and triggering an automatic cleaning mechanism to clean the TWS transition version resources when the TWS transition version resources are used.

Description

Production processing method and device for TWS transition version

Technical Field

The invention relates to the technical field of data processing, in particular to a method and a device for producing TWS transition versions.

Background

This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.

The large commercial bank uses TWS (Tivoli Workload Scheduler, enterprise operation scheduling software) to manage and maintain based on the batch of the IBM host, and in order to ensure business stability and diversity, release and production of versions can be routinely arranged every month, and meanwhile, the advanced version and the postponed version can be released according to needs of business and the like. For TWS version, publishing and production content is divided into a core batch version and a transition batch version, wherein the core batch version generates and executes a current day plan routinely every day according to running period, ETT (Event-triggeredtracking) loading and other modes, and version content is reused according to settings; the transition batch version is mainly a matched version production release, and the related content is only used once when the version is produced.

In the existing application scenario, core batch version production time is generally arranged in the morning on sunday. The prior proposal adopts a set of TWS shared by the core batch version and the transition batch version, the overseas is divided into 4 sets of TWS according to time zones, the version is put into production, the transition batch TWS content is put into production at night on the T-2 day, the generation time of the T-1 day plan is relied on, and the transition batch version content is loaded into the T-1 day plan. And before the current day plan is generated in each environment of the T day, the TWS flow is emptied, the core batch TWS version is put into production, and the current day plan generated on the T day is ensured to no longer contain the contents of the transition batch TWS version. Meanwhile, after the version production is finished, each TWS set needs to check the T-1 day plan, and the unexecuted contents in the plan are manually cleaned.

The TWS version deployment is carried out by utilizing the prior art, overseas core batches generate batch plans regularly every day, and the TWS is shared with the core batches, so that the operation cannot be carried out until the batch plans of the same day are generated after the transition version is thrown. If an emergency patch exists, the situation that the release is carried out along with the arrival can not be achieved, and the release deployment efficiency is affected. Moreover, the transition batch is only used for version production, and the risk of false triggering exists in the TWS, so that the transition content needs to be cleaned in time. The cleaning process presents the following risks: because the TWS is shared by the transition and the core, the core content needs to be cleaned together and then reloaded when the transition content is cleaned, and the risk of core batch ETT loading failure exists in the period; the TWS flows of the core and the transition are mixed, and the risks of misoperation exist in the process of clearing the transition and reloading the core content.

In summary, the prior art mainly has the defects of low efficiency, false triggering risk in the transition batch, and the like, and a technical scheme capable of overcoming the defects is needed.

Disclosure of Invention

In order to solve the problems in the prior art, the invention provides a method and a device for producing TWS transition version, which are used for checking a transition TWS version, analyzing a transition version scheduling file, generating a TWS transition version script, producing TWS transition version resources after the script is checked and passed, and effectively cleaning after the resources are used, so that the production and the use safety and stability of the new scheme of the down transition version are ensured, the accuracy and the efficiency of the TWS transition version production are improved, and the production risk is reduced.

In a first aspect of an embodiment of the present invention, a method for commissioning a TWS transitional version is provided, including:

acquiring a transition version scheduling file of the TWS, checking the transition version scheduling file according to preset conditions, and releasing the transition version scheduling file after the checking is passed;

analyzing the transition version scheduling file to obtain script parameter information;

reading a transition version script template of the TWS, and generating a TWS transition version script according to the script parameter information and the transition version script template;

obtaining a script effective time point, a script data list and a catalog of an operation entity according to the TWS transition version script, and checking the TWS transition version script;

after the verification is passed, loading TWS transition version resources according to the TWS transition version script;

and triggering an automatic cleaning mechanism to clean the TWS transition version resources when the TWS transition version resources are used.

In a second aspect of the embodiment of the present invention, a device for processing a production of a TWS transitional version is provided, including:

the checking module is used for acquiring a transition version scheduling file of the TWS, checking the transition version scheduling file according to a preset condition, and releasing the transition version scheduling file after the checking is passed;

the analysis module is used for analyzing the transition version scheduling file to obtain script parameter information;

the generation module is used for reading the transition version script template of the TWS and generating a TWS transition version script according to the script parameter information and the transition version script template;

the auditing module is used for acquiring a script effective time point, a script data list and a catalog of an operation entity according to the TWS transition version script, and auditing the TWS transition version script;

the loading module is used for loading the TWS transition version resources according to the TWS transition version script after the auditing is passed;

and the cleaning module is used for triggering an automatic cleaning mechanism to clean the resources of the TWS transition version when the resources of the TWS transition version are used.

In a third aspect of the embodiments of the present invention, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements a method for commissioning a TWS transitional version when executing the computer program.

In a fourth aspect of the embodiments of the present invention, a computer readable storage medium is provided, where a computer program is stored, and when executed by a processor, the computer program implements a method for commissioning a TWS transitional version.

In a fifth aspect of the embodiments of the present invention, a computer program product is presented, the computer program product comprising a computer program, which when executed by a processor, implements a method of commissioning a TWS transitional version.

According to the method and the device for producing the TWS transition version, the transition version scheduling file of the TWS is obtained, the transition version scheduling file is checked according to preset conditions, and the transition version scheduling file is issued after the check is passed; analyzing the transition version scheduling file to obtain script parameter information; reading a transition version script template of the TWS, and generating a TWS transition version script according to the script parameter information and the transition version script template; obtaining a script effective time point, a script data list and a catalog of an operation entity according to the TWS transition version script, and checking the TWS transition version script; after the verification is passed, loading TWS transition version resources according to the TWS transition version script; when the resources of the TWS transition version are used, an automatic cleaning mechanism is triggered to clean the resources of the TWS transition version, the whole scheme can realize the full-flow processing of version issuing, generating, putting into production and cleaning of the TWS transition version, the version deployment mode is flexible, the putting into production risk can be reduced, the resource utilization rate is effectively improved, and powerful technical support is provided for TWS management and maintenance.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic flow chart of a method for commissioning a TWS transitional version according to an embodiment of the invention.

FIG. 2 is a flow chart of a method for checking transitional version scheduling according to an embodiment of the present invention.

FIG. 3 is a flow chart of a method for generating a transitional version script according to an embodiment of the present invention.

FIG. 4 is a flow chart of an audit TWS transition version script according to an embodiment of the present invention.

FIG. 5 is a schematic flow chart of automatic production according to an embodiment of the present invention.

FIG. 6 is a schematic flow chart of automatic cleaning according to an embodiment of the invention.

FIG. 7 is a schematic diagram of a TWS transition version of a production processing device according to an embodiment of the present invention.

FIG. 8 is a schematic diagram of a computer device according to an embodiment of the invention.

Detailed Description

The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are presented merely to enable those skilled in the art to better understand and practice the invention and are not intended to limit the scope of the invention in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art will appreciate that embodiments of the invention may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.

According to the embodiment of the invention, a method and a device for producing TWS transition version are provided, and the method and the device relate to the technical field of data processing.

In the embodiments of the present invention, terms to be described are as follows:

1. TWS: tivoli Workload Scheduler is a set of enterprise workload management programs for unified planning, management, control, and automated scheduling of mainframe batch jobs, while also allowing manual intervention in batch planning. In the present invention, the Z/OS version, i.e., the host-side version, is mainly referred to.

2. TWS version: the large commercial bank regularly issues batch schedule versions for meeting business requirements or ensuring stable production, and the large commercial bank is divided into a core batch version and a transition batch version.

3. SR: a Special Resource (SR) corresponds to a switch concept, for example, a day-end batch start operation is triggered by the SR, and all subsequent batches start to run according to the set order. In a general case, SR represents a specific resource in a system, where some of the resources are needed during the running of a batch job, where the resources are unavailable for a certain period of time, the batch job is unable to run, waiting is needed, and once a specific resource is available, the status of the resource is made available, and then the batch job that depends on the resource can begin running.

4. ETT: event-triggered tracking, an Event-triggered process, which is a function that is not runcyclic in TWS, and is usually submitted at an irregular time; an AD running sporadically is added, i.e. ADD, to the current PLAN to run, although it may be provided with a context in the original PLAN, etc. The triggering of ETT generally uses SR triggering, so the ETT triggered ADs all have SRs.

5. AD: application Descriptions, referred to as a job group, is a collection of a group of jobs having the same attribute. In a huge batch process, there may be many jobs that perform similar functions, only one service is completed, and their operation periods are the same, so it is not necessary to define an operation period for each job, an AD may be defined, and jobs that perform similar functions and have the same operation period are put into the AD, only one operation rule needs to be defined for the AD, so all jobs belonging to the AD have the same operation rule. A maximum of 256 jobs can be contained in one AD, and the total number of jobs cannot be exceeded.

Within the TWS, the minimum unit of operation rules is AD, but not job, and if each job must have a different operation rule, then it is required that a job belongs to an AD.

The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments thereof.

Fig. 1 is a schematic flow chart of a method for commissioning a TWS transitional version according to an embodiment of the invention. As shown in fig. 1, the method includes:

s101, acquiring a transition version scheduling file of TWS, checking the transition version scheduling file according to preset conditions, and releasing the transition version scheduling file after the checking is passed;

s102, analyzing the transition version scheduling file to obtain script parameter information;

s103, reading a transition version script template of the TWS, and generating a TWS transition version script according to the script parameter information and the transition version script template;

s104, obtaining a script effective time point, a script data list and a catalog of an operation entity according to the TWS transition version script, and checking the TWS transition version script;

s105, after the auditing is passed, loading TWS transition version resources according to the TWS transition version script;

and S106, triggering an automatic cleaning mechanism to clean the resources of the TWS transition version when the resources of the TWS transition version are used.

According to the method for producing the TWS transition version, the transition version scheduling file is analyzed through checking the transition TWS release, the TWS transition version script is generated, the TWS transition version resources are produced after the script is checked and passed, and the TWS transition version resources are effectively cleaned after the resources are used, so that the safety and stability of production and use of the TWS transition version under the new scheme are ensured, the accuracy and efficiency of production of the TWS transition version are improved, and the production risk is reduced.

In order to more clearly explain the above-mentioned production processing method of the TWS transition version, the following will describe each step in detail.

In S101, a transitional version schedule file of the TWS is obtained, the transitional version schedule file is checked according to a preset condition, and after the check is passed, the transitional version schedule file is issued, and the specific flow is as follows:

reading the file content of the transition version scheduling file to obtain an operation group name, an operation name and a partition identification;

and if the check determines that the name of the job group does not exist a rename, the job name does not exist a rename, and the comparison and the identification of the comparison result are consistent with the currently selected partition, the migration version scheduling file is issued.

In an actual application scene, the TWS transition version is considered to be used once only when the version is put into production, and in order to save production resources, the invention adopts four sets of overseas TWS transition versions to be combined into the same TWS environment. Based on the scene, the operation names of different entities in all overseas environments are required to be different, and no operation front-back item dependency relationship exists between different overseas environments; in this regard, in the transitional version schedule, a preset condition (i.e., a mandatory specification) is formulated, and all the version contents must meet the following conditions:

the overseas migration is divided into 4 partitions, each partition batch number is determined, and each partition batch number is independent and has no intersection. The migration version schedule provides the choice of the overseas partition to which it belongs, and the TWS schedule allows only one partition to be selected for non-batched migration AD (job directory) and jobs.

For non-batch migration operations, the last bit of the fixed job name is the partition identifier, e.g., O, E, A, X indicates the asian, euler, american, and college, respectively.

In one embodiment, based on the preset conditions, the present invention performs normalization inspection on the transitional version schedule, and the main flow includes: reading the migration version scheduling file, after checking the file format and authority, reading the file content, analyzing the scheduling content piece by piece, acquiring the parameter value of the partition after judging the AD name and the job name are not re-named, and checking whether the last-bit partition identifier of the job name is consistent with the selected partition.

Referring to FIG. 2, a flow chart of a method for checking transitional version schedule according to an embodiment of the invention is shown. As shown in fig. 2, the specific flow is as follows:

s201, acquiring the TWS scheduling file name and address.

S202, whether a transition version schedule file is acquired or not; if not, the error reporting file does not exist; if so, S203 is performed.

S203, reading the file.

S204, checking file authority and format; if the file authority is insufficient or the format is wrong, checking that the file is not passed, and ending the flow; if the file has the right and the format is correct, S204 is executed.

S205, analyzing file content, and obtaining parameter values such as AD, job name, partition and the like.

S206, judging whether the AD contains an expander; if not, executing S207; if so, S208 is performed.

S207, judging whether the AD has a rename or not; if yes, prompting that the AD has a rename, and ending the flow; if not, S208 is performed.

S208, judging whether the job name contains an expander; if so, S209 is performed; if not, S210 is performed.

S209, judging whether the job has a rename; if so, prompting that the job has a rename, and ending the flow; if not, S210 is performed.

S210, analyzing and obtaining the last character of the job name.

S211, judging whether the end character of the job is matched with the environment; if the characters are not matched, prompting that the tail characters of the job name are not matched with the environment, and ending the process; if so, S212 is performed.

S212, the transition version schedule file passes the examination, the transition version schedule file is issued, and the current flow process is ended.

In S102, the transition version schedule file is parsed to obtain script parameter information.

Wherein, the script parameter information at least comprises: job group name, job group attribute, job name, constraint relationship, and partition identification.

In S103, reading a transition version script template of the TWS, and generating a transition version script of the TWS according to the script parameter information and the transition version script template, wherein the specific flow is as follows:

importing the job group name, the job group attribute, the job name, the constraint relation and the partition identifier into a transition version script template of the TWS to generate a job entity; if the job group name and the job name comprise batch extension symbols, automatically extending the job group name and the job name according to the partition identification;

and deploying the operation entity in the catalogue corresponding to each partition according to the partition.

In a specific embodiment, after the normal line sets the TWS running period and the TWS necessary parameters, reading a TWS script template; and analyzing the checked transition version scheduling file piece by piece to obtain information such as an AD name, AD attributes (such as control conditions such as running period, ETT, SR and the like), operation names, constraint relations (such as timing, front-back item constraint and the like), belonging partitions and the like, and if the AD names and the operation names contain batch expansion symbols $, automatically expanding according to partition batch numbers to finally form TWS scripts.

Simultaneously, when the job names are acquired or expanded, the corresponding job templates are synchronously read, and the job entities are automatically generated and deployed in different catalogues according to different partitions.

Referring to fig. 3, a flowchart of a transitional version script generation process according to an embodiment of the present invention is shown. As shown in fig. 3, the specific flow is as follows:

s301, inputting effective time and TWS environment parameters.

S302, reading and analyzing to obtain the TWS version script template.

S303, reading the TWS scheduling file and reading the record.

S304, analyzing the record and obtaining the parameter information.

S305, judging whether the AD contains an expander; if so, S306 is performed; if not, S307 is performed.

S306, obtaining the partition number of the partition according to the partition and automatically expanding the AD name.

S307, judging whether the job name contains an expander; if so, S308 is performed; if not, S309 is performed.

S308, obtaining the partition number of the partition according to the partition and performing automatic extension operation name.

S309, reading a job template; if the reading fails, prompting that the operation template is abnormal; if the reading is successful, S310 is performed.

S310, generating a job entity.

S311, importing the job group name, the job group attribute, the job name, the constraint relation and the partition identification into a transition version script template of the TWS to generate a TWS transition version script.

In S104, according to the TWS transition version script, a script effective time point, a script data list and a catalog where an operation entity is located are obtained, and the TWS transition version script is audited, which specifically includes the following steps:

comparing the script effective time point of the TWS transition version script with a preset effective time;

comparing the script data list with the list of the test center script; wherein, the script data list at least comprises: an operation group list, an operation list, a control list and a script total line number;

checking the job name in the job entity catalog;

and when the script effective time point is consistent with the preset effective time, the script data list is consistent with the list of the test center script, and when the job name in the job entity catalog does not have a duplicate name, the TWS transition version script passes the audit.

In a specific embodiment, the step mainly completes automatic inspection and audit of the generated TWS transition version script and the operation entity before production, and avoids production events caused by abnormal installation, abnormal effectiveness or misoperation of operation and error call in the execution process of the TWS transition version caused by inconsistent effective time point parameters, operation rename and repeated operation entity in the script.

The main process of the step comprises the following steps: reading and analyzing the produced TWS transition version script, acquiring effective time point parameters, comparing, and confirming that the effective time points are consistent; acquiring an AD list, an operation list, an SR list and an ETT list through script analysis, simultaneously counting the total number of lines of the scripts, and comparing the acquired results with the list of the test center script and the statistical results to ensure that the handover content is consistent with the handover content of the test center; analyzing and acquiring the catalog of the operation entity, and checking and confirming that the rename operation does not exist in the catalog.

Specifically, referring to fig. 4, a flowchart of an audit TWS transition version script according to an embodiment of the invention is shown. As shown in fig. 4, the specific flow is as follows:

s401, reading TWS transition version script.

S402, analyzing and obtaining effective time.

S403, judging whether the effective time is consistent with the preset effective time; if so, S404 is performed; if not, prompting that the effective time is inconsistent, ending the flow.

For example, the preset effective time of domestic and large-line environments is 9:00; euro is 12:00; sub-6:00, etc.

S404, analyzing and acquiring an AD list and a job list.

S405, judging whether the analysis data is consistent with the handover list; if yes, execute S406; if not, prompting that the resource list is inconsistent, outputting a check result, and ending the flow.

S406, counting the resource quantity and the script length.

S407, judging whether the statistical data is consistent with the handover resource number; if yes, execute S408; if not, prompting that the resource numbers are inconsistent, ending the flow.

S408, analyzing the job catalog and acquiring job name information of each catalog.

S409, judging whether the file name is unique; if yes, the auditing is passed; if not, prompting that the file name is not unique, outputting an abnormal file name list, and ending the flow.

In S105, after the audit is passed, loading the resources of the TWS transitional version according to the TWS transitional version script, which specifically includes:

stopping TWS when the set time period is reached, and backing up the TWS in the current queue;

after the backup is completed, the TWS in the current queue is emptied, and the TWS transitional version script is loaded one by one;

checking the number of the TWS resources in real time in the script loading process, if the number of the TWS resources is consistent with the preset number of the TWS resources through comparison, backing up the current resources, and loading TWS transition version resources in the current queue;

starting the TWS and monitoring the running state of the TWS.

In a specific embodiment, the step may implement automatic commissioning and inspection functions of the TWS transitional version and automatic cleaning functions after version implementation is completed.

The step uses TWS flow to realize automatic production of the transitional version, and the main process comprises the following steps: triggering an ETT loading automatic production process by opening an SR switch in a change time period; and after the SR switch is controlled by the first job, the prepared version installation job is automatically invoked and automatically executed according to the dependency relation, wherein the method comprises the steps of backing up original resources, clearing TWS resources, automatically loading transitional versions, counting and checking the number of the resources, backing up new resources and automatically generating a planned effective new version.

Specifically, referring to fig. 5, a schematic flow chart of automatic production according to an embodiment of the present invention is shown. As shown in fig. 5, the specific flow is as follows:

s501, switching on SR.

S502, closing the TWS switch.

S503, backing up the original TWS flow.

S504, the TWS flow is cleared.

S505, the TWS transition flow is automatically loaded piece by piece.

S506, checking and acquiring the TWS real-time resource number.

S507, comparing whether the number of resources is consistent; if yes, executing S508; if not, the number of resources is inconsistent, and the process is ended.

Specifically, after the installation of a certain environmental script is completed, it is required to determine whether the number of resources is consistent with the preset number of resources. According to the test handover, the number of script resources in each environment has a preset value, such as the AD number, the SR number and the like, and the preset value is recorded in a script configuration file; in an actual application scene, after the installation of one environment is completed, acquiring the number of each resource finally loaded, respectively comparing the number with a preset value, and if the number of the resources is completely consistent, indicating that the number of the resources meets the expectation, and continuing the next operation; otherwise, the number of the prompt resources is inconsistent.

S508, backing up the new resources.

S509, automatically generating a new plan effective transition version.

S510, turning on the TWS switch.

S511, checking whether the TWS state is normal; if yes, the state is normal; if not, the TWS state is abnormal, and the process is ended.

In S106, when the use of the resources of the TWS transitional version is completed, an automatic cleaning mechanism is triggered to clean the resources of the TWS transitional version, and the specific flow is as follows:

stopping TWS when the use of the TWS transition version resource is finished, inquiring the incomplete operation in the TWS current day plan, and modifying the state of the incomplete operation to be finished;

cleaning the TWS transition version resource in the job queue, and exporting a cleaning success list;

starting the TWS and monitoring the running state of the TWS.

In a specific embodiment, after the version production is used, the SR switch is turned on, and an automatic cleaning mechanism is triggered, including the steps of turning off the TWS switch, acquiring the work and AD in the non-completed state, automatically setting the work and AD in the completed state, deleting the content of the TWS transition version in the base library, and turning on the TWS switch.

Specifically, referring to fig. 6, a schematic flow chart of automatic cleaning according to an embodiment of the invention is shown. As shown in fig. 6, the specific flow is as follows:

s601, turning on SR.

S602, closing the TWS switch.

S603, inquiring and acquiring unfinished conditions in the TWS current day plan in real time.

S604, checking whether incomplete AD exists; if yes, execution S605; if not, S606 is performed.

S605, the automation sets the AD as completed.

S606, automatically clearing TWS transition version contents in the base library.

S607, inquiring and acquiring a resource list in the base library in real time.

S608, checking whether cleaning is completed; if so, S609 is performed; if not, the cleaning fails and an unclean success list is output.

S609 turns on the TWS switch and checks the TWS state.

S610, judging whether the state is normal; if yes, ending the flow; if not, sending out TWS state abnormality prompt.

The invention separates the migration and version integrated production contents of four overseas partitions from the core TWS, integrates the content into a set of TWS environment for operation, further adopts a newly added overseas migration TWS edition issuing rule, newly adds an overseas migration TWS edition checking and cleaning tool, adjusts MV tool parameters, TWS system configuration and the like, and ensures the safety and stability of the production and the use of the new scheme migration version.

Compared with the prior art, the invention has at least the following advantages:

1. the version is flexibly deployed. After the overseas migration TWS is split, the generation of the migration lot plan is not limited by the time of the generation of the core lot plan any more, and the instant effect of the lot plan can be realized. For the transition version, a batch plan can be flexibly generated and put into production according to application requirements. Therefore, the whole time from installation to production of the planned version is greatly shortened, rapid deployment along with the arrival of the emergency patch can be realized, and the production efficiency of the version is improved.

2. And the production risk is reduced. The overseas migration TWS is split, so that the overseas migration TWS is separated from the core TWS, migration and core version production are independent, the influence of modification and cleaning of the migration version on core batch is prevented, and the safety of version production is improved.

3. The resources are utilized effectively. The TWS special for production has low utilization rate, and TWS transition versions multiplex the existing TWS, so that the utilization rate of TWS production is effectively improved.

It should be noted that although the operations of the method of the present invention are described in a particular order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the particular order or that all of the illustrated operations be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

Having described the method of an exemplary embodiment of the present invention, next, a production processing apparatus of a TWS transitional version of an exemplary embodiment of the present invention will be described with reference to fig. 7.

The implementation of the production processing device of the TWS transition version can be referred to the implementation of the method, and the repetition is not repeated. The term "module" or "unit" as used below may be a combination of software and/or hardware that implements the intended function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Based on the same inventive concept, the invention also provides a device for processing the production of TWS transition version, as shown in FIG. 7, the device comprises:

the checking module 710 is configured to obtain a transitional version schedule file of the TWS, check the transitional version schedule file according to a preset condition, and issue the transitional version schedule file after the check passes;

the parsing module 720 is configured to parse the transition version schedule file to obtain script parameter information;

the generating module 730 is configured to read a transitional version script template of the TWS, and generate a transitional version script of the TWS according to the script parameter information and the transitional version script template;

an auditing module 740, configured to obtain a script effective time point, a script data list and a catalog where an operation entity is located according to the TWS transition version script, and audit the TWS transition version script;

the loading module 750 is configured to load the resources of the TWS transitional version according to the TWS transitional version script after the audit is passed;

and the cleaning module 760 is configured to trigger an automatic cleaning mechanism to clean the resources of the TWS transitional version when the resources of the TWS transitional version are used.

In one embodiment, the inspection module 710 is specifically configured to:

In one embodiment, the script parameter information obtained by the parsing module 720 at least includes: job group name, job group attribute, job name, constraint relationship, and partition identification.

In one embodiment, the generating module 730 is specifically configured to:

In one embodiment, the auditing module 740 is specifically configured to:

checking the job name in the job entity catalog;

In one embodiment, the loading module 750 is specifically configured to:

starting the TWS and monitoring the running state of the TWS.

In one embodiment, the cleaning module 760 is specifically configured to:

starting the TWS and monitoring the running state of the TWS.

It should be noted that although several modules of a TWS transitional version of a commissioning processing device are mentioned in the above detailed description, this partitioning is merely exemplary and not mandatory. Indeed, the features and functions of two or more modules described above may be embodied in one module in accordance with embodiments of the present invention. Conversely, the features and functions of one module described above may be further divided into a plurality of modules to be embodied.

Based on the foregoing inventive concept, as shown in fig. 8, the present invention further proposes a computer device 800, including a memory 810, a processor 820, and a computer program 830 stored in the memory 810 and capable of running on the processor 820, where the processor 820 implements the foregoing method for commissioning the TWS transition version when executing the computer program 830.

Based on the foregoing inventive concept, the present invention proposes a computer readable storage medium storing a computer program which, when executed by a processor, implements the method for commissioning a TWS transitional version as described above.

Based on the foregoing inventive concept, the present invention proposes a computer program product comprising a computer program which, when executed by a processor, implements a method of commissioning a TWS transitional version.

In the technical scheme, the acquisition, storage, use, processing and the like of the data all accord with the relevant regulations of laws and regulations.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Finally, it should be noted that: the above examples are only specific embodiments of the present invention, and are not intended to limit the scope of the present invention, but it should be understood by those skilled in the art that the present invention is not limited thereto, and that the present invention is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. The method for producing the TWS transition version is characterized by comprising the following steps:

2. The method of claim 1, wherein obtaining a transitional version schedule file of the TWS, checking the transitional version schedule file according to a preset condition, and releasing the transitional version schedule file after the checking is passed, comprises:

3. The method according to claim 1, wherein the script parameter information includes at least: job group name, job group attribute, job name, constraint relationship, and partition identification.

4. The method of claim 3, wherein reading a transitional version script template of the TWS, generating a TWS transitional version script based on the script parameter information and the transitional version script template, comprises:

5. The method of claim 1, wherein obtaining a script validation time point, a script data list, and a catalog in which an operating entity is located according to the TWS transitional version script, and auditing the TWS transitional version script comprises:

checking the job name in the job entity catalog;

6. The method of claim 1, wherein loading the resources of the TWS transitional version according to the TWS transitional version script after the audit passes comprises:

starting the TWS and monitoring the running state of the TWS.

7. The method of claim 1, wherein triggering an automatic cleaning mechanism to clean up the TWS transitional version of the resource when the TWS transitional version of the resource is used up comprises:

starting the TWS and monitoring the running state of the TWS.

8. A production processing device for a TWS transitional version, comprising:

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 7 when executing the computer program.

10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 7.

11. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the method of any of claims 1 to 7.